On Apr 6, 2011, at 11:49 AM, Daniel Macks wrote:

> On Wed, 6 Apr 2011 08:32:44 -0400, Charles Lepple  wrote:
>> Along those lines, if it looks like a package needs to depend on  
>> fink-
>> obsolete-packages, I'm putting my vote in for adding that dependency
>> when you modify the description. (Although I see AKH just posted a
>> good argument for not doing that if the obsolete package doesn't have
>> its own info file.)
>
> "obsolete" has the technical meaning of "has dependency on f-o-p".  
> This
> is just about adding an obvious Description for these technically
> obsolete packages. There are lots of other packages that have newer
> alternatives, but may require various changes to switch to them, so  
> the
> old ones are not as definitely "no reason to be using this old thing".
> So if a package got renamed or diffused into another package, the old
> name would be an obsolete one because there is no reason to continue  
> to
> use it. The old package is just a dummy pointing to the new one. But  
> if
> there is an old library-version (libgettext3-{dev,shlibs} vs
> libgettext8-{dev,shlibs}), the old one is still a real separate set of
> files and completely appropriate to use in certain cases due to binary
> linking and such.

While I agree that it is necessary to keep around the -shlibs for old  
library versions, I guess I'm thinking that there should be a hint to  
developers that the -dev splitoff they are depending on has been  
superseded. (This isn't always obvious from the package names - see  
libpng or expat.)


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to