On Sat, Mar 27, 2010 at 06:15:17AM +0200, lu...@proxima.alt.za wrote:
> > 4) Once compilation is done, you create a package that is simply a
> > tarball with the stuff that needs to be installed, a script and a _map_
> > that tells : this thing here shall be put there, with owner: owner:group
> > and permissions: permissions.
>
> Should this be a proto? Just in case you've overlooked the option, no
> offence intended.
The bit of lacking information that leads to false conclusions: I
use my own framework (built for KerGIS) that is at the moment
strictly POSIX oriented. Hence, at least as a first step---since
if it's far more easy to redo the work from an old Web2c than to
try to deal with the present monstruosity, it's still some work...---,
the Plan9 flavor will come in an APE fashion---for the building
framework and the installation framework (sh(1)), simply because it's
there; for code per se, I'm tidying TeX things for C89, period.---.
There are numerous things that are a problem to deal with on Unix like
systems, and that are far easier on Plan9. That's probably why we are
here? But I'm still using Unices, so TeX has to install on Unices and
Plan9.
So, what I wanted to say is: it will probably not be pure Plan9 at
first (for installation); but it should be trivial to adapt to whatever
one sees fit, and it will need less time to anyone to adapt than to
argue about taste.
--
Thierry Laronde (Alceste) <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
