Okay, another idea. Consider for major versions N:
fooN.info:
Package: fooN
Version: N.0.0
SplitOff: <<
Package: foo-dev
Provides: fooN-dev
<<
The fooN packages are empty (like Type: bundle). By having all the
major versions of the -dev be arranged as different %v of the same %n,
their installation are mutually exclusive. They all conflict with and
replace one another but they don't have to explicitly list all others
as Conflicts/Replaces). A dependency on fooN-dev causes dpkg to
automatically install the version of foo-dev that provides it (handled
as a simple %v upgrade/downgrade). This works in simple tests. The
only problem I've seen so far is that since fooN-dev are virtual, one
cannot manually 'fink build' or 'fink install' them (which IMO borders
on being a bug in its own right). But if you know what's going on, you
can interact with foo-dev-%v.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
