19 червня 2011 о 18:07 +0100 Chris Lamb написав(-ла): > > Becasue of this I think it will be good to have some sort of api virtual > > package (like swi-prolog(-nox)?-api-<some number>), provided by > > swi-prolog-* packages and some helper (dh_swi_prolog?) to fill depends > > field of spark (and any other future packages). > > Okay, in addition to this wouldn't we also need to go through NEW for each > API bump also we need to detect these API bumps in the first place? No, the control file for swi-prolog-nox should contain something like this:
Provides: swi-prolog-vm-01234567
And control file for spark source could contain this:
Depends: ${swipl:VM-Version}
That could become this in binary package (after using dh_swi_prolog):
Depends: swi-prolog-vm-01234567
This way there should be no need to change package name, but it will
require bin-NMUs for all depending packages (that is only spark for
now).
The provides field in swi-prolog package can be filled by some script
that looks for VM_SIGNATURE value during package build, so no manual
changes will be required.
Looking at src/pl-wic.c, maybe LOADVERSION (or VERSION) needs to be taken
into account too in virtual package name, but I'm not sure
> (As an aside, I finished my university studies that require SWI-Prolog a
> long time ago - would you like to adopt the package?)
Well, I only need swi-prolog for spark package and I know only basics of
Prolog. If you deside to orphan the package, I could take it. But
otherwise I prefer it to be maintained by someone who knows prolog. But
I could help with implementing the solution for this bug, if you agree
with it.
Regards,
Eugeniy Meshcheryakov
signature.asc
Description: Digital signature
