On Mon, Jul 11, 2005 at 03:51:28PM -0400, Koen van der Drift wrote: > > On Jul 11, 2005, at 2:03 AM, Daniel Macks wrote: > > >One solution is to > >create a final old-name-2.0-1:Depends:new-name(>=2.0-1) but is > >Type:bundle and has a Description noting that it's just a upgrade > >compatibility game. That way his old old-name will be out-of-date, and > >when he upgrades it he will get he'll get the new one. > > That sounds like a good plan. If I use Type: bundle, how do I add the > variants, so that the user can define the python version she wants to > use?
I think same as usual...multivariants give you every combination of the choice sets. And omitting an explicit for a type key set means "there's only one choice for this key", so the long-existing Type:bundle is now just a special case of the generic variant syntax. Perhaps: Package: foo-py%type_pkh[python] Type: bundle, python (2.3 2.4) would give you packages foo-py23 and foo-py24, each of Type:bundle. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
