public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Gregory M. Turner" <gmt@malth.us>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: removing "server" profile variants from profiles.desc
Date: Fri, 12 Oct 2012 04:43:18 -0700	[thread overview]
Message-ID: <50780256.7070500@malth.us> (raw)
In-Reply-To: <CANSUr=+yJnwe2ZTei378zeNcUY_m6PMxh+iK2ZK7C+3RwW2_Cw@mail.gmail.com>

On 10/11/2012 3:31 PM, Ben Kohler wrote:
> There are other ways to achieve a "lighter" system, but that's not really
> what this is about.  The server profiles are not any lighter than the base
> profiles.
>
> To those in favor of keeping some kind of "server" profile around, how
> would it differ from the base profile?  What would you enable or disable on
> top of the base?  I am pretty sure that the current USE="-perl -python snmp
> truetype xml" is not what any of you would suggest.
>
> In my opinion, removing /usr/portage/profiles/targets/server/make.defaults
> and having the "server" target apply nothing over the base profiles, and
> then dropping the warning from the server profiles, would be a better
> situation than where we are now.
>
> -Ben

That seems pretty reasonable.

Another possibility, I suppose, would be to combine Rich's idea with 
yours and get:

   base -> minimal -> server (noop)

Also super-easy if we just build the above cascade, take what's in 
server, move it into minimal, git rid of the awful warning, and call it 
fixed.

At least by clarifying what is meant by "server", we might inspire 
someone to contribute more enhancements later.

Kind of the opposite of your original proposal, Ben :P

At least we've established broad consensus that the warning should be 
silenced.

-gmt


  reply	other threads:[~2012-10-12 11:44 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 [this message]
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
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=50780256.7070500@malth.us \
    --to=gmt@malth.us \
    --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