On Fri, Jul 06, 2007 at 07:54:20PM +0200, Claudio Sacerdoti Coen wrote:
> Well, not really (at least in theory).
> You can just run the old camlp4 once to translate the source to standard
> syntax and then package the translated sources. In principle this could
> be done at every new upstream release. It could be bad debian practice,
> though.
This is an interesting idea.
It might become however not practical in the long run: today I have the
old camlp4 installed in unstable and I can run it to translate ledit
source code. At the next ledit release (but remember that here "ledit"
is just an example, we might have a lot of apps with the same issue) it
might be more difficult, and having to compile by hand camlp4s just to
translate the code of ledit is definitely ugly.
However we can package camlp4s, no matter how many conflicts at the
filesystem level it creates (we can either let it Conflicts: with other
stuff or heavily rename its executables), and use it just as a build
dependency of legacy application to translate at build time legacy code
to code that does not require camlp4 for building at all.
That will also solve Sven's license concerns, on which I agree.
Cheers.
[1] Sven: last time I checked the code was decent enough to be read,
let's say not worst than yet-another-way of indenting OCaml that you can
find in the average OCaml application out there :)
--
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/
(15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the
(15:57:15) Bac: no, la demo scema \/ right keys at the right time
Attachment:
signature.asc
Description: Digital signature