On Mon, Sep 12, 2005 at 09:27:45AM -0700, jt wrote:
> On Sun, Sep 11, 2005 at 12:04:08AM +0200, Guus Sliepen wrote:
> > Hello Jean,
> >
> > 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'
Here is how it works. All the wireless tools are built with an
explict dependancy on the proper version of iwlib. I currently have
installed on my system both Wireless Tools version 27 and 28, and it
work perfect.
As the tools are always in-sync with the lib, there is never
any problem, and they can use the lastest 'pre' version of the
lib. This allow you to introduce newer versions of the tools as you
wish.
Other apps really want to use the latest stable version of the
lib ('libiw27' in our case). Most of them will take time to use the
latest feature of iwlib, so won't suffer from that. Depending on the
latest stable guarantee those apps stability and avoid the present
problem.
Actually, if you are really worried about those apps, just
don't make the 'libiw28-dev' package, this way they are forced to only
compile with 'libiw27-dev'.
Now, the trick is that when I release WT-28 and WT-29-pre1,
you will need some deep magic to get the migration right.
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).
Have fun...
Jean
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
