
A great many Haskell packages on AUR are out of date, whether marked as such or not. Only the 300 or so packages in [haskell] receives any sort of love, but even that is very spotty. Based on this I think it's most honest to disown the vast majority of packages on AUR owned by arch-haskell. Any thoughts or comments on this? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay

On Mon, Nov 7, 2011 at 11:18 AM, Magnus Therning
Any thoughts or comments on this?
But there is also cases like qtHaskell that are not straightforward to build by hand, and it is not in hackage. That should have a [aur] if not present in [haskell] In most cases since cabal does a better job, [aur] packages should be strongly discouraged.

On Mon, Nov 7, 2011 at 21:01, Bernardo Barros
On Mon, Nov 7, 2011 at 11:18 AM, Magnus Therning
Any thoughts or comments on this?
But there is also cases like qtHaskell that are not straightforward to build by hand, and it is not in hackage. That should have a [aur] if not present in [haskell]
qtHaskell is special, because it's not on Hackage. That's why it isn't in [haskell].
In most cases since cabal does a better job, [aur] packages should be strongly discouraged.
IMNSHO we should never look at cabal as a replacement for an Arch repo or [aur]. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

On Tue, Nov 8, 2011 at 10:32 AM, Magnus Therning
On Mon, Nov 7, 2011 at 21:01, Bernardo Barros
wrote: On Mon, Nov 7, 2011 at 11:18 AM, Magnus Therning
Any thoughts or comments on this?
But there is also cases like qtHaskell that are not straightforward to build by hand, and it is not in hackage. That should have a [aur] if not present in [haskell]
qtHaskell is special, because it's not on Hackage. That's why it isn't in [haskell].
In most cases since cabal does a better job, [aur] packages should be strongly discouraged.
IMNSHO we should never look at cabal as a replacement for an Arch repo or [aur].
How do you make the distinction between using cabal-install and [haskell] in you day-to-day use. I tend to use cabal-install for developpement and [haskell] for production. But often the two are quite close and I end up trying to add these packages to [haskell]. There is also issues with cabal-install itself and in combination to Arch. For instance cabal-install will build/install a package which may exists in [haskell]. Does anyone have a solution for that? Second, there is no cabal-uninstall and packages are easily broken by Arch updates. -- Nicolas Pouillard http://nicolaspouillard.fr

On Tue, Nov 8, 2011 at 11:11, Nicolas Pouillard
On Tue, Nov 8, 2011 at 10:32 AM, Magnus Therning
wrote: On Mon, Nov 7, 2011 at 21:01, Bernardo Barros
wrote: On Mon, Nov 7, 2011 at 11:18 AM, Magnus Therning
Any thoughts or comments on this?
But there is also cases like qtHaskell that are not straightforward to build by hand, and it is not in hackage. That should have a [aur] if not present in [haskell]
qtHaskell is special, because it's not on Hackage. That's why it isn't in [haskell].
In most cases since cabal does a better job, [aur] packages should be strongly discouraged.
IMNSHO we should never look at cabal as a replacement for an Arch repo or [aur].
How do you make the distinction between using cabal-install and [haskell] in you day-to-day use.
I don't use cabal-install, so it's simple to make the distinction :) /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

On Tue, Nov 8, 2011 at 12:53 PM, Magnus Therning
On Tue, Nov 8, 2011 at 11:11, Nicolas Pouillard
wrote: On Tue, Nov 8, 2011 at 10:32 AM, Magnus Therning
wrote: On Mon, Nov 7, 2011 at 21:01, Bernardo Barros
wrote: On Mon, Nov 7, 2011 at 11:18 AM, Magnus Therning
Any thoughts or comments on this?
But there is also cases like qtHaskell that are not straightforward to build by hand, and it is not in hackage. That should have a [aur] if not present in [haskell]
qtHaskell is special, because it's not on Hackage. That's why it isn't in [haskell].
In most cases since cabal does a better job, [aur] packages should be strongly discouraged.
IMNSHO we should never look at cabal as a replacement for an Arch repo or [aur].
How do you make the distinction between using cabal-install and [haskell] in you day-to-day use.
I don't use cabal-install, so it's simple to make the distinction :)
OK, so I misunderstood «we should never look at cabal as a replacement for an Arch repo or [aur].»?
From this I read that you do want make cabal-install useless in Arch?
-- Nicolas Pouillard http://nicolaspouillard.fr

On Tue, Nov 8, 2011 at 13:20, Nicolas Pouillard
On Tue, Nov 8, 2011 at 12:53 PM, Magnus Therning
wrote: On Tue, Nov 8, 2011 at 11:11, Nicolas Pouillard
wrote: On Tue, Nov 8, 2011 at 10:32 AM, Magnus Therning
wrote: On Mon, Nov 7, 2011 at 21:01, Bernardo Barros
wrote: On Mon, Nov 7, 2011 at 11:18 AM, Magnus Therning
Any thoughts or comments on this?
But there is also cases like qtHaskell that are not straightforward to build by hand, and it is not in hackage. That should have a [aur] if not present in [haskell]
qtHaskell is special, because it's not on Hackage. That's why it isn't in [haskell].
In most cases since cabal does a better job, [aur] packages should be strongly discouraged.
IMNSHO we should never look at cabal as a replacement for an Arch repo or [aur].
How do you make the distinction between using cabal-install and [haskell] in you day-to-day use.
I don't use cabal-install, so it's simple to make the distinction :)
OK, so I misunderstood «we should never look at cabal as a replacement for an Arch repo or [aur].»? From this I read that you do want make cabal-install useless in Arch?
No, I meant no such thing. pacman (with repos) and cabal-install are at best complementary, and often they aren't even that. This means we can't say that dropping [aur] OK because users can always turn to cabal-install. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

On Mon, Nov 7, 2011 at 8:18 PM, Magnus Therning
A great many Haskell packages on AUR are out of date, whether marked as such or not. Only the 300 or so packages in [haskell] receives any sort of love, but even that is very spotty. Based on this I think it's most honest to disown the vast majority of packages on AUR owned by arch-haskell.
Any thoughts or comments on this?
I agree to either disown them or remove them. -- Nicolas Pouillard http://nicolaspouillard.fr

On Tue, Nov 08, 2011 at 07:18:13AM +0100, Nicolas Pouillard wrote:
On Mon, Nov 7, 2011 at 8:18 PM, Magnus Therning
wrote: A great many Haskell packages on AUR are out of date, whether marked as such or not. Only the 300 or so packages in [haskell] receives any sort of love, but even that is very spotty. Based on this I think it's most honest to disown the vast majority of packages on AUR owned by arch-haskell.
Any thoughts or comments on this?
I agree to either disown them or remove them.
+1 -Linus

On Mon, Nov 07, 2011 at 08:18:56PM +0100, Magnus Therning wrote:
A great many Haskell packages on AUR are out of date, whether marked as such or not. Only the 300 or so packages in [haskell] receives any sort of love, but even that is very spotty. Based on this I think it's most honest to disown the vast majority of packages on AUR owned by arch-haskell.
Any thoughts or comments on this?
Based on the comments so far I'm about to try to orphan all package on AUR, except for the 300+ that currently are in [haskell]. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. -- Alan Kay
participants (4)
-
Bernardo Barros
-
Linus Arver
-
Magnus Therning
-
Nicolas Pouillard