I wanted the second set because I may want to establish the link even if I'm not the maintainer of the second package.
I would imagine that the second set of actions would be otherwise identical, and the link would show up on either package regardless of which set of verbs was used. Antoine On May 25, 2011 12:50 PM, <qu...@sparq.org> wrote: > Quoting Antoine Latter <aslat...@gmail.com>: > >> On May 25, 2011 11:08 AM, "KQ" <qu...@sparq.org> wrote: >> > >> > The HackageDB could the provide this information in the description page >> of a package, and it could even automatically cross-reference and supplement >> the referred package descriptions, so that if you are looking at the Parsec2 >> page it will also show a section "This package has a Redesign: parsec3. >> The redesign states: ...[Information]......". This type of information >> can help people know what the alternatives are for various packages and a >> general understanding of the reason for the proliferation of packages >> (without having to search haskell-cafe and stack-overflow archives for some >> discussion that provided the justification/recommendations). >> > >> > Thoughts? >> > >> >> The only thing I'd add would be the additional actions "ReplacedBy", >> "ExtendedBy" and "RedesignedBy". >> >> Antoine > > I was actually thinking that this was the part that HackageDB could do > automatically on the page that the actionBy applied to. There should be enough > information in the DB (somewhat like Roel's reverse dependencies work) and the > alternative would be having to re-release a package (that you don't necessarily > own) to add the actionBy field. > > -KQ > > > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
