I intend to take over bluefish, which has been released by the  
previous maintainer.  This package currently has three variants:

bluefish
bluefish-gnome2       # with gnome2, with vfs enabled
bluefish-gnomevfs2  # with gnome2, but with vfs disabled

I find the last variant name (bluefish-gnomevfs2) inconsistent with  
the fact that vfs is disabled.  I would like to change the name of  
this variant to "bluefish-gnome2-novfs".  I believe that this would  
improve clarity.

I need advice on the best way to handle the transition from the  
current variant name structure to the new one.  Anyone who has  
bluefish-gnomevfs2-1.0.6 should be automatically upgraded to bluefish- 
gnome-novfs2-1.0.7.  At first glance, this looks like a job for  
Replaces/Conflicts, but I do not understand how I would do this for  
only one variant.  The package currently has Replaces/Conflicts on  
all variants:

Replaces: bluefish, bluefish-gnome2, bluefish-gnomevfs2
Conflicts: bluefish, bluefish-gnome2, bluefish-gnomevfs2

Kevin Horton
Ottawa, Canada



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to