"Vesa" == <vpkaihla@gmail.com> writes:
Vesa> Nevertheless, why adopt a package that wasn't out-of-date without Vesa> doing anything to it? Especially when you already have more than Vesa> 700? I'm more disturbed by the fact that he is adopting packages which are clearly maintained by others, e.g. see header of gtk2hs pkgbuild: # Maintainer: Sergej Pupykin <sergej@aur.archlinux.org> # Maintainer: Vesa Kaihlavirta <vegai@iki.fi> # Contributor: Arch Haskell Team <arch-haskell@haskell.org> which shows: a) there is Arch Haskell Team that handles (almost) all of the Haskell packages in Arch and b) there is already maintainer for the package Moreover, adding line as # Maintainer: Sergej Pupykin <sergej@aur.archlinux.org> could imply that he just blindly (via some scripts) does his job of 'maintaining' packages which he (most probably) does not use at all :-( In the above example of gtk2hs it is well known that the gtk2hs-0.9.10 deprecates 'sourceview' component in the favor of 'gtksourceview2' and he just blindly bumped up the old version. Otoh, AUR shows 740 pkgs belonging to him and one is a little bit suspicious what kind of quality one can provide with so many of them :-/ I know he was already subject of the discussion, but it is known (amongst Haskell hackers) that Arch is (one of) the best Haskell-supported distro available with the dedicated team of Devs/Tus taking care about the quality of all the packages prior of entering into extra/community, so taking over Haskell packages is, imho, just a sign of extensive greediness to increase the number of adopted packages and not sign of desire to provide quality support. Sincerely, Gour -- Gour | Zagreb, Croatia | GPG key: C6E7162D ----------------------------------------------------------------