Hi Євгеній,
> > 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 contro
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-), provided by
> > swi-prolog-* packages and some helper (dh_swi_prolog?) to fill depends
> > field of spark (and any other futu
Євгеній Мещеряков wrote:
> Becasue of this I think it will be good to have some sort of api virtual
> package (like swi-prolog(-nox)?-api-), 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
Package: swi-prolog-nox
Version: 5.10.4-1
Severity: normal
Hello,
I'm maintaining a package that build-depends on swi-prolog-nox and
contains non-native prolog executables (spark). The problem is that
upgrade of swi-prolog-nox to 5.10.4-1 breaks spark that was compiled
with earlier version of swi
4 matches
Mail list logo
