On Sun, Jan 16, 2011 at 10:44:10PM +0100, Seblu wrote:
Yes great. I'm not paid by package i maintain. Do not misunderstand my intentions, this package is more often used without gtk (subjective). It's a really useful package for debugging network issues and got it in a server is a plus. Server => no gtk => no user repository packages. This was my reasoning.
I didn't mean to be offensive at all - just in case you misunderstood my mail. I just wondered if we should include the same package with different sets of compilation options in [community] at the same time. In my understanding, the Arch Way implies that there shouldn't be hundreds of versions with different patches or compilation options in the repositories, but only a single package that provides a working environment with sane defaults and as little patching as possible. Users, who would like to have some feature enabled/disabled, can use the ABS to build modified packages and can upload such modified packages to the AUR if they want to share them. Of course, there are exceptions. boinc-nox and emacs-nox are probably in the repos because there's a large number of users that don't need X support and building customized packages takes a while (just a guess). So if there's a good reason to include mtr-cli as well, I don't have any objections.
If you see my comment on the package, fstrim will be included in next release of util-linux-ng. So forget :)
's alright then. Just wondered as it was in the list of packages you'd like to include in [community] :)