Defunct packages (was: inotify bindings)
Sorry about that. Can you delete system-inotify from Hackage? Probably best not to have two, almost identical, packages.
Putting this in a more general perspective - how do you mark a package in Hackage defunct? If there's a newer package with the same name superceding an older one then it's not a problem. But if you have no newer package, what then? To be specific, I'm wondering what to do with the hspr package that will be discontinued in the new upcoming HSP release. It would be great to have a flag somewhere that marks it deprecated. Cheers, /Niklas
niklas.broberg:
Sorry about that. Can you delete system-inotify from Hackage? Probably best not to have two, almost identical, packages.
Putting this in a more general perspective - how do you mark a package in Hackage defunct? If there's a newer package with the same name superceding an older one then it's not a problem. But if you have no newer package, what then?
To be specific, I'm wondering what to do with the hspr package that will be discontinued in the new upcoming HSP release. It would be great to have a flag somewhere that marks it deprecated.
Yes, marking things as either "broken" or "deprecated", and filtering them from the default view, would be a good feature. -- Don
On Fri, 2008-03-21 at 10:56 -0700, Don Stewart wrote:
niklas.broberg:
Sorry about that. Can you delete system-inotify from Hackage? Probably best not to have two, almost identical, packages.
Putting this in a more general perspective - how do you mark a package in Hackage defunct? If there's a newer package with the same name superceding an older one then it's not a problem. But if you have no newer package, what then?
To be specific, I'm wondering what to do with the hspr package that will be discontinued in the new upcoming HSP release. It would be great to have a flag somewhere that marks it deprecated.
Yes, marking things as either "broken" or "deprecated", and filtering them from the default view, would be a good feature.
Right, we'd need to record that extra bit of information. There is a generic tags mechanism we could take advantage of for storage. We should file a feature request: http://hackage.haskell.org/trac/hackage/newticket Duncan
We should file a feature request:
http://hackage.haskell.org/trac/hackage/ticket/261 Cheers, /Niklas
On Fri, 2008-03-21 at 20:38 +0100, Niklas Broberg wrote:
We should file a feature request:
Thanks. I've added a comment and marked it as being reasonably easy. Don't take that as a sign that the overworked hackage maintainers will do it, take it as a message that any interested hacker should be able to grab the code and craft a patch. :-) darcs get --partial http://darcs.haskell.org/hackage-scripts/ Duncan
participants (3)
-
Don Stewart -
Duncan Coutts -
Niklas Broberg