"Benedikt Morbach" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Thu, 14 Aug 2008 21:56:16 +0200:
> Possible solutions include: (sorted by necessary effort) 1. Leaving > everything like it is (not a real solution) 2. Removing the imlib2 > useflag 3. Changing the 24 ebuilds depending on imlib2 to use the imlib2 > useflag (and possibly making it a global flag) > > In my opinion, making imlib2 a global useflag would be the best > solution, as it gives users who do not want an ancient unmaintained > library a fine grained control over their system. Good catch/argument. Based on what was done with qt and gtk, option 2 above, removing the imlib2 USE flag and converting everything to use the imlib USE flag, is the most likely solution. Check the archives on gtk/gtk2 if you'd like. In the gtk/gtk2 case, where many packages could link against either, gtk was used to toggle the gtk general preference, while gtk2 if enabled indicated a preference for it over gtk(1). The solution was to deprecate the gtk2 flag and in general prefer gtk2 to gtk(1), if both could be linked. Individual package maintainers could of course decide to prefer gtk(1) if there was an overriding reason to do so. (qt had somewhat different details which I don't fully recall ATM, but I don't believe it's quite as direct a parallel in any case.) Since you mentioned that no imlib/imlib2 packages seem to use both flags, that solution would seem even more applicable here. Just do away with the imlib2 flag entirely, and prefer imlib2 in any cases where there is now or may be later a choice unless there's an overriding reason not to. But while I follow the discussion here regularly and have done so for some time, I'm just a user. We'll see what the devs have to say. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
