What to do when upstream breaks configuration

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/10/2011 08:37 AM, Mat Booth wrote:
> On 10 January 2011 13:02, Stephen Gallagher <sgallagh at redhat.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> As a caveat, this is a project that always requires at least some manual
>> intervention on upgrade, as individual sites need to have an upgrade
>> script run on them. So end-users are used to taking some action.
>> Unfortunately, upstream did not include this configuration change into
>> the upgrade script (mostly because the location of this configuration
>> file isn't guaranteed on all platforms) so it will require an additional
>> step by the users.
>>
> 
> 
> Can you not patch the upgrade script so that it works? Presumably the
> location of this configuration file is known for Fedora....


No, it's not. It's an arbitrarily-named Apache config file dropped into
the apache httpd.conf.d (or symlinked in there from elsewhere).

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0rFKkACgkQeiVVYja6o6ODBwCghCbBcEU/3ybmP9dBQWQ6HpUw
sq0AnivdWj++qXxLZ5ZGrsLXTxIVjx+1
=sQXz
-----END PGP SIGNATURE-----