[Pkg-jed-devel] error building jed_0.99.16.pre.0.99.17.84-1

[Jörg Sommer]

--gj572EiMnwbLXET9
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

G. Milde schrieb am Mon 18. Apr, 09:50 (+0200) :
> On 15.04.05, J=F6rg Sommer wrote:
> > G. Milde schrieb am Fri 15. Apr, 15:17 (+0200) :
> > > On 15.04.05, J=F6rg Sommer wrote:
> > > > I would prefer:
> > > >
> > > > if (getenv("NO_JED_CONF") =3D=3D NULL)
> > > >   do_jed_conf();
> > >=20
> > > % debian jed.conf as suggested by John E. Davis
> > > % Read the documentation in /usr/share/doc/jed-common/README.Debian-s=
tartup.
> > > % Please do not change this if you want the documented debian startup=
 system
> > > % to function correctly.
> > >=20
> > > if (getenv("JED_SKIP_INIT_D") !=3D NULL)
> > > {
> > >  $1 =3D listdir ("/etc/jed-init.d");
> >=20
> > This was also my idea, but it doesn't work. We can't manipulate the
> > jed.conf of the current installed version. The only way is, to prevent =
it
> > from coming up.
>=20
> Unfortunately, I do not see a way to prevent jed.conf from coming up in t=
he
> installed version (as I suppose we cannot manipulate site.sl either).
>=20
> However, we could try to eliminate the bug for the more-than next
> versions by providing a means to skip jed_init.d in jed.conf of the next
> jed package.

But jed will never buildable if a version lower than this is installed.
Think of the jump from sarge to etch. From this point of view or package
will never buildable and I don't know if this is a policy violation.

> * if John doesnot like a new command line arg just for Debian, we could
>   still "emulate" it in jed.conf by looking at __argv and killing the
>   spurious "argument buffer". As this argument is rather seldom used, the
>   overhead of the spurious buffer would not seriusly harm.

This is ugly.

> > And the same problem would occure with /u/l/etc/jed.conf and
> > /u/etc/jed.conf. We can't change any of this files while building and
> > they all make the build fail, because their expected files aren't in the
> > path.
>=20
> Do you mean /usr/local/etc/jed.conf and /usr/etc/jed.conf?

Yes.

> AFAIK, these two were never used by Debian, so a Debian package doesnot
> need to take of them explicitely.

No. I see the bugreport coming: "If I have a local jed.conf in
/usr/local/etc/jed.conf (which is FHS conform) I can not build jed."

We can't hobble debian users and admins with such assumtions.

> Alternatively we could make sure that files in /etc/jed_init.d do the
> appropriate checks with e.g.
>    search_path_for_file()                        for single files and
>    is_substr("my_dir", "get_jed_library_path")   for directories

This prevents overlaying files and package versions by a local version by
placing them before the real version in jed_library_path.

--=20
- StGB =A7=A7 328 Absatz 2, Nr.3 : Mit Freiheitsstrafe bis zu
f=FCnf Jahren oder mit Geldstrafe wird bestraft, wer eine
nukleare Explosion verursacht.

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

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

iQEVAwUBQmPkg4Z13Cz2nwVYAQJ6cwgAgxB8vG00qYLQL1e86CnfQ+uUnqqqnGs0
uL72dLk/wgBx+ImKxN6j1NppCth9BQKUjIVMkreNbLCseHcUpa0/MQuMsAiMPkh4
O2RTAqJEarlsrzf1OORH9zDewZJmqjddRg1TGR5Brkk431K+Ed1AgFaohd4R7b/x
TtMqILND8d8shpsnNE5TUaHfRh5K5/7BGLyau1f1zAeJAWUToWjk1jAJM69OuhSO
Lh4KJmwu0SKDp7GCPmNyypc81E7RNkam2pJylpTZ+RPPjqgaTjQTKSic8eJIw7DF
ZCn+MSI5Nn8tpXOl4sriP9E9EpDcZ1zpY7onrezin9G8tMT8OrSQAA==
=OVY4
-----END PGP SIGNATURE-----

--gj572EiMnwbLXET9--