Re: [Haskell-cafe] Handling absent maintainers

2010-07-23 Thread Alexander Dunlap
One issue that comes up is that when you fork a package, data can no longer be freely exchanged between libraries using the original package's datatypes and libraries using the forked package's datatypes. Something that might help here is the concept of "extension" or "friend" packages or modules:

Re: [Haskell-cafe] Handling absent maintainers

2010-07-23 Thread Mark Wotton
That works fine for my own stuff, but I'd like it to work for people using my software that relies on those packages. mark On Sat, Jul 24, 2010 at 4:10 PM, Roman Beslik wrote: >  I patch broken packages in my local repository. I increment a version so > the local repository get a precedence over

Re: [Haskell-cafe] Handling absent maintainers

2010-07-23 Thread Roman Beslik
I patch broken packages in my local repository. I increment a version so the local repository get a precedence over the Hackage. On 16.07.10 03:54, Mark Wotton wrote: 2. run my own hackage server and tell my users to use that instead. -- Best regards, Roman Beslik. ___

Re: [Haskell-cafe] Handling absent maintainers

2010-07-15 Thread Ivan Lazar Miljenovic
Alexander Solla writes: > On Jul 15, 2010, at 6:49 PM, Jason Dagit wrote: > >> Everyone has their own branch of everything they contribute to, >> listed right on the website? This is inline with another idea I've >> heard where we'd have a 'stable' hackage and 'unstable/dev' >> versions. But,

Re: [Haskell-cafe] Handling absent maintainers

2010-07-15 Thread Mark Wotton
On Fri, Jul 16, 2010 at 11:49 AM, Jason Dagit wrote: > > > On Thu, Jul 15, 2010 at 5:54 PM, Mark Wotton wrote: >> >> Ideally, I'd like to be able to say something like "cabal install >> my-hacked-package --as original-package" - are there fundamental >> reasons that wouldn't be possible, or a bad

Re: [Haskell-cafe] Handling absent maintainers

2010-07-15 Thread Alexander Solla
On Jul 15, 2010, at 6:49 PM, Jason Dagit wrote: Everyone has their own branch of everything they contribute to, listed right on the website? This is inline with another idea I've heard where we'd have a 'stable' hackage and 'unstable/dev' versions. But, how does this work for resolving

Re: [Haskell-cafe] Handling absent maintainers

2010-07-15 Thread Jason Dagit
On Thu, Jul 15, 2010 at 5:54 PM, Mark Wotton wrote: > Hello all, > > I've recently had problems with haskell-src-meta. While it's a great > package, it doesn't currently compile on GHC 6.12, and Matt Morrow > doesn't seem to be around to push the version that does to Hackage. > Our "one-world" ap

[Haskell-cafe] Handling absent maintainers

2010-07-15 Thread Mark Wotton
Hello all, I've recently had problems with haskell-src-meta. While it's a great package, it doesn't currently compile on GHC 6.12, and Matt Morrow doesn't seem to be around to push the version that does to Hackage. Our "one-world" approach with cabal seems to discourage forking as a casual act, so