(I think this didn't go to the list...trying again, and with corrections to example at the end)
Martin Costabel <[EMAIL PROTECTED]> said: > Daniel Macks wrote: > [] >> You're getting yourself *way* too worked up about variants, Martin. > > I get worked up about anything that doesn't work correctly. In this > case, I gave a bug report to Michèle. There needs to be an upgrade path > from bluefish to bluefish-gnome2. Right now it breaks. > > In addition, I am really curious how the variant system handles this. Is > there a possibility to say (as a packager): Exactly one of the variants > can be installed, and every one of them can replace the others? Each would set a Conflicts/Replaces against all others...same way we do it now with different X for fooX and fooX-dev. Maintainer manually lists every variant (a lot of typing I know...there are some ideas for less verbose ways, but not implemented yet) in the Conflicts/Replaces. Fink knows that it doesn't make sense for a package to Conflicts or Replaces itself, so it silently and automatically removes a package from its own lists. Something like: Package: gimp%type_pkg[-noprint] Type: -noprint (boolean) Conflicts: gimp, gimp-noprint Replaces: gimp, gimp-noprint dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
