[Haskell-cafe] Unmaintained packages and hackage upload rights

Ben Gamari bgamari.foss at gmail.com
Thu Jan 30 16:53:56 UTC 2014

Clark Gaebel <cgaebel at uwaterloo.ca> writes:

> How does the process of taking over maintenance add latency to your work?
> 1) Check out broken version of package.
> 2) Fix locally, bump version number locally.
> 3) cabal sandbox add-source ../fixed-package in any package that needs the
> fixed version.
> 4) Email hackage admins for upload rights.
> 5) Continue working on your actual project.
> 6) Receive upload privileges one day.
> 7) Upload fixed package.
> As far as I can tell, the only real latency cost here is that paid to fix
> the broken version.
In my experience, step 4 involved several round trips between a number
of different people. Admittedly, this is in part because it's easy to
forget about the broken package after you have fixed it locally.


- Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20140130/6af834f7/attachment.sig>

More information about the Haskell-Cafe mailing list