[mercury-users] best practices for packaging libraries

Peter Ross pro at missioncriticalit.com
Mon Jul 9 19:50:38 AEST 2012

On 7 July 2012 15:35, Sean Johnson <sean at snootymonkey.com> wrote:
> Michael,
> What are the libraries? I'm curious.
> I think a packaging system is probably a bit ambitious right now given the
> amount of 3rd party library activity there is. But maybe someday. We can
> hope.
> One suggestion would be to put each of your libraries in a public github
> repo. Then we can have a wiki list of Mercury libraries that's linked from
> the mercurylang.org site. Authors of new libraries can simply add their
> library's public repo to the wiki with a description of what it does.
> What do you all think of that idea? If someone with access to
> mercurylang.org likes it enough to add the link, and you Michael like it
> enough to start with your libraries, I'll take it upon myself to set up the
> wiki page.
> Seems better than the mercury_extras approach which is then in CVS and out
> of the control of the 3rd party library developer, not open to forking and
> pull requests, etc.
I think that is an excellent idea, if you create the wiki page then I
can add a link to it to the Mercury home page.

mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au

More information about the users mailing list