[Pkg-jed-devel] byte compiling sl files

[Jörg Sommer]

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

G. Milde schrieb am Tue 26. Apr, 10:43 (+0200) :
> On 25.04.05, J=F6rg Sommer wrote:
> > G. Milde schrieb am Mon 25. Apr, 12:57 (+0200) :
> > > > 1) Each package needing byte-compiling
> > >=20
> > >      * can do this in the postinst script with:
> > >     =20
> > >          cd <dir where the file is installed, e.g. Jed_Site_Library>
> > >          jed --batch -f 'byte_compile_file("<myfile.sl>", 0)'
> >=20
> > and didn't get updated if a new jed package comes.
>=20
> It gets updated by 3), if it is in Jed_Site_Library

But I see, it doesn't get builded, because jed-common doesn't depend on
jed. If realizing this idea leads to every package depends on "(jed |
xjed)" (and later maybe on (... | fljed)). And if xjed is installed, you
can't call jed. (The same with fljed)

> This would mean an addition to the standard jed package, however I
> consider it to be non-invaive as it doesnot change the behaviour of jed.
> At least, it in not more invasive than the add-on of the jed-init.d
> directory already in place.

Why JED does not add it to its package? It there a reason for it?

> With home-lib, jed-common would also provide (and initialize)
> Jed_Site_Library for other packages (jed-extra or any other). So packages
> that want to provide a mode for jed do not depend on jed-extra in order
> to have a a space to put their files in. (/etc/jed-init.d should be
> reserved for as few as possible and as small as possible initialization
> files, to ensure a fast startup of jed.)

You are right. This would be an improvement. I'm not really happy mixing
jed and jed-extra, but it has its advantage.

> > > > 3) The jed-common package will run=20
> > >=20
> > >      cd <Jed_Site_Library>
> > >      jed --batch -l make_ini.sl
> >=20
> > Which fails.
>=20
> This is bad.  Of course, in order to be in jed-common, make_ini.sl needs
> to be stable and tested.
>=20
> Why does it fail? Could you try the attached version?

The same as above: jed might not be installed and you don't know which
version of jed (jed, xjed, fljed) is going to install.

J=F6rg.

--=20
The UNIX Guru's View of Sex:
# unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sle=
ep

--raC6veAxrt5nqIoY
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)

iQEVAwUBQm5RPYZ13Cz2nwVYAQKpQwgA1YEBbMk6E3fkvLyZrg/VbJei6FZFa/KI
xViJ3IGVIGFnty+5v5RElrXMxpW+1RA/+nkTyxaf1458QgOYJunxLj9wsmyvSCmN
DI0ceG3rFhJgoRHBYkMnkO0sjIDk+e4P3O4qf112VEWuiTDl+elBKt5Q5oIWZfxd
+Xc90c0/K7JUaAB6n+W3FQkPHq1S1FWw1hdvccm30rCuuT7GAITUgArtBSL5rt+/
wFw7q+qPR0wE7RU/ZE/qY2oN8z3HmPyOiO0VgzFsDT/59ERhRJ9dYboBWaYflDnC
5wNN0TykNNCBSKyGIdoUtmyquI/Cg/LlZnTuizyAOISpAiK2m7C5rA==
=+zgQ
-----END PGP SIGNATURE-----

--raC6veAxrt5nqIoY--