Wrong location for plugin-specific configuration?

[Thomas Schmidt]

--bp/iNruPH9dso1Pn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Darren Salt schrieb am 07.08.04, um 14:15 Uhr:
> >>  * Used strace to find out what was being accessed, and was surprised =
to
> >>    find mention of /var/lib/vdr/plugins/plugin.xine.conf.
>=20
> > It seems that we missed this as we changed the path of the cfg-files to=
 be
> > FHS-compliant. Changing the $PLUGIN_CFG_DIR in vdr.default should fix t=
his
> > also and is a little bit more simple as the postinst-version. :)
>=20
> This is true. OTOH, it's possible that people have already put files in
> /var/lib/vdr/plugins...

Hmm, do you think, that it is necessary to add some code for this in
postinst?


Thomas

--=20
Thomas Schmidt
thomas.schmidt@in.stud.tu-ilmenau.de

--bp/iNruPH9dso1Pn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBF11xc9+NqwoydlIRAo+mAJ9w6uYaVzsGRWK1GRnnvUMyEQEg/gCcDZPc
pEynAFeGCeYRBMozxsdGlqY=
=hQnR
-----END PGP SIGNATURE-----

--bp/iNruPH9dso1Pn--