From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: removing "server" profile variants from profiles.desc
Date: Fri, 12 Oct 2012 10:11:19 +0100 [thread overview]
Message-ID: <CAG2jQ8g-DBaqSPpEB6faztz8rRGtoY=z2h4vTJNGwV+ro+GbmQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_nmUV4_6Zg90=zm-E+FyK0EOkd8mAJtG=kK4mwFgjUArw@mail.gmail.com>
On Fri, Oct 12, 2012 at 9:18 AM, Rich Freeman <rich0@gentoo.org> wrote:
> On Fri, Oct 12, 2012 at 4:08 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
>> +1. I want these profiles to *staty*. I am using this profile on my
>> "home boxes". It is the most minimal profile as the rest of the
>> profiles pull in too much useless stuff. What is wrong with these
>> profiles anyway?
>
> Looking at the actual profiles themselves, using server vs the base
> profile makes these changes:
> USE="-perl -python snmp truetype xml"
>
> So, you're getting less perl/python support, but you're getting snmp,
> truetype, and xml.
>
> I think overall you'd get a more minimal setup with the base profile,
> and if you really want -perl/-python you could just set those in your
> USE. I'd think that your home box would be more likely to benefit
> from perl/python support on packages than having snmp support. But,
> to each his own...
>
> I'd be all for there being an actual minimal profile, but I don't
> think server really is that.
>
> Rich
>
Removing python and perl support is good enough to justify that this
profile is "minimal" ;)
Moreover, snmp is something you really want in 24/7 boxes. Anyhow, I
see no reason to remove these profiles just
because they are 'similar' to the base profile. But I do agree to
remove the ewarn message as it a bit annoying if you
update such systems often enough.
--
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
next prev parent reply other threads:[~2012-10-12 9:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 18:56 [gentoo-dev] Proposal: removing "server" profile variants from profiles.desc Ben Kohler
2012-10-11 19:03 ` Peter Stuge
2012-10-11 19:22 ` Mike Frysinger
2012-10-11 19:29 ` Rich Freeman
2012-10-11 20:04 ` Walter Dnes
2012-10-11 22:22 ` Gregory M. Turner
2012-10-11 22:31 ` Ben Kohler
2012-10-12 11:43 ` Gregory M. Turner
2012-10-12 8:10 ` Markos Chandras
2012-10-12 8:08 ` Markos Chandras
2012-10-12 8:18 ` Rich Freeman
2012-10-12 9:11 ` Markos Chandras [this message]
2012-10-12 13:53 ` Mike Gilbert
2012-10-12 14:13 ` Ben Kohler
2012-10-12 14:29 ` Daniel Pielmeier
2012-10-14 10:00 ` Markos Chandras
2012-10-14 15:42 ` Ben Kohler
2012-10-14 19:54 ` Markos Chandras
2012-10-15 4:22 ` Mike Frysinger
2012-10-15 11:28 ` Rich Freeman
2012-10-15 15:20 ` Zac Medico
2012-10-15 17:45 ` Mike Frysinger
2012-10-30 8:17 ` Mike Frysinger
2012-10-17 15:06 ` Ben Kohler
2012-10-18 0:37 ` Peter Stuge
2012-10-18 8:34 ` Markos Chandras
2012-10-12 12:46 ` Sergey Popov
2012-10-12 13:36 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG2jQ8g-DBaqSPpEB6faztz8rRGtoY=z2h4vTJNGwV+ro+GbmQ@mail.gmail.com' \
--to=hwoarang@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox