On Fri, Sep 16, 2005 at 06:39:38PM -0700, Jean Tourrilhes wrote: > > > It appears programs using libiw28 break with the latest version of > > > wireless-tools, unless you recompile them. Now, I know that 27 is the > > > stable version and 28 is still only "pre", but I want to know if this > > > was intentional or not. > > > [...] > > I believe one way to fix the overall problem would be to > > always keep the stable version of iwlib (version 27 in our case)... > > Guus, > > Here are the packages you are going to do : > > 1) package 'libiw27' built from WT-27 > 2) package 'libiw27-dev' built from WT-27 > > 3) package 'libiw28' built from WT-28 > 4) package 'libiw28-dev' built from WT-28 > 5) package 'wireless-tools' built from WT-28 > > 'libiw27' and 'libiw28' can coexist, 'libiw28' does not > deprecate 'libiw27', the user can install both on the system. > 'libiw27-dev' and 'libiw28-dev' conflict. > 'wireless-tools' depend on 'libiw28'
To do that properly, I would be better if libiw was packaged separate
from the wireless-tools by you. I can't do it with two source packages,
because both would build "wireless-tools" debs, which would conflict
with eachother, unless I rename the wireless-tools package to
wireless-tools27 and wireless-tools28, which is clearly undesirable.
The other option is that I keep stable versions of wireless-tools in the
unstable distribution, but upload the -pre versions to experimental. That
reduces the number of people that will install the -pre versions though.
A third option is that you increase the soname whenever you change the
API (yes, even increasing the length of some buffer counts as an API
change), even if it happens in the middle of -pre versions.
> Another advantage is that this scheme would allow you to avoid
> beeing blocked by the freeze (it would only apply to WT-27, not
> WT-28).
Yes. But on the other hand stable users might expect to use stable
libraries for all the programs they install, so maybe the -pre version
shouldn't end up in stable at all.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
