Re: Proposal: splitting the network package

On Tue, Feb 5, 2013 at 12:40 AM, Johan Tibell wrote:

On Thu, Jan 31, 2013 at 10:05 PM, Michael Snoyman wrote:

...

Many users won't be able to upgrade to the new network library immediately. However, adding an extra dependency on (an essentially empty) network-uri is perfectly feasible. My approach makes it possible for library authors to make their code compatible with both network 1.4 and 1.5 with just a single line change.

If you want to see examples that were more painful from the author perspective, consider the previous merging of network and network-bytestring, or the blaze-markup/blaze-html split. Both of them required adding cabal flags and conditionals to every user package that wanted to work with both versions, which definitely caused some headaches.

Someone ought to write a "How to split a package" and a "How to merge two packages" guide that carefully lists out the steps and the pros and cons of the approach.

-- Johan

I'll be happy to write such a guide. But I'd like to get some consensus on whether the approach I've sketched out so far is acceptable, particular for packages in the HP. Michael