public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Kohler <bkohler@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: removing "server" profile variants from profiles.desc
Date: Wed, 17 Oct 2012 10:06:48 -0500	[thread overview]
Message-ID: <CANSUr=JAM62WAGB8g3MapjZbwBhS-O6xiZ=LSW3M9DmM=wcNiA@mail.gmail.com> (raw)
In-Reply-To: <201210150022.51254.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]

On Sun, Oct 14, 2012 at 11:22 PM, Mike Frysinger <vapier@gentoo.org> wrote:

>
> please stop top posting.  you're making a mess of this whole thread.
>
> sounds like we should extend the profiles.desc file or profile structure to
> include a description so that people know the intention of each one.  the
> only
> marker we had before was implicitly in the name (".../server" and
> ".../desktop").
> -mike
>

Sorry about that.

The addition of this extra info about the profiles sounds great, but back
to the original issue-- what *is* the intention of the server target?
 Right now it seems like nothing more than a broken outdated vanity title,
for people who feel that using a "standard" profile on a server is icky.
 No one actually believes that the server target's USE flags make any
sense, and no one has proposed what they SHOULD be.  All that seems to be
established is a general feeling "don't take away our server profiles".

Whether it's time to flat out *remove* those profiles, I don't know.  But
if these profiles aren't going to be updated or maintained in any way, I
believe that new users should be shielded from them.  They are not a viable
or sensible choice for ANY new installation.  In my ideal world ("if I were
king"), today I would delist them from profiles.desc, and send out a news
item warning of their immediate deprecation and planned removal 3 months
from now.

-Ben

[-- Attachment #2: Type: text/html, Size: 1909 bytes --]

  parent reply	other threads:[~2012-10-17 15:07 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
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 [this message]
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='CANSUr=JAM62WAGB8g3MapjZbwBhS-O6xiZ=LSW3M9DmM=wcNiA@mail.gmail.com' \
    --to=bkohler@gmail.com \
    --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