From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs
Date: Fri, 19 Aug 2005 02:01:28 +0900 [thread overview]
Message-ID: <20050818170128.GA487528@lion.gg3.net> (raw)
In-Reply-To: <200508181628.44059.trapni@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
maillog: 18/08/2005-16:28:40(+0200): Christian Parpart types
>
> Using the "minimal" useflag for this - IMHO - is a misuse of the idea of
> "minimal" semantically - as I do understand minimal in a way like "don't
> overbloat me with patches and other feature additions"-alike.
minimal - Install a very minimal build (disables, for example, plugins,
fonts, most drivers, non-critical features)
vanilla - Do not add extra patches which change default behaviour
The way you understand "minimal" seems to be closer to what "vanilla" is
used for. By "feature additions" I assume that you mean "extra
functionality added by patches".
Note the subtle difference -- "minimal" disables default functionality
(provided upstream) while "vanilla" disables patched-in functionality.
Of course, there is the "server" use flag that mysql could use with
great success.
--
-* Georgi Georgiev -* "So, will the Andover party have a cash -*
*- chutz@gg3.net *- bar?" "No, there's free beer." "Uh-oh, *-
-* +81(90)2877-8845 -* Stallman's gonna be pissed..." -- -*
*- ------------------- *- overheard at the Bazaar, 1999 *-
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-18 17:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 14:28 [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs Christian Parpart
2005-08-18 14:23 ` Luca Barbato
2005-08-18 15:24 ` Francesco R
2005-08-18 14:27 ` Brian Jackson
2005-08-18 14:40 ` Mike Frysinger
2005-08-18 15:13 ` Lance Albertson
2005-08-18 15:24 ` Ciaran McCreesh
2005-08-18 15:28 ` Francesco R
2005-08-18 15:37 ` Chris Gianelloni
2005-08-18 15:56 ` Brian Harring
2005-08-18 16:08 ` [gentoo-dev] Local USE defaults Donnie Berkholz
2005-08-18 16:31 ` Brian Harring
2005-08-18 17:16 ` Alec Warner
2005-08-18 17:36 ` Brian Harring
2005-08-18 17:18 ` Mike Frysinger
2005-08-18 17:38 ` Brian Harring
2005-08-19 7:10 ` Donnie Berkholz
2005-08-19 11:53 ` Brian Harring
2005-08-18 17:24 ` [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs Ciaran McCreesh
2005-08-18 18:13 ` Brian Harring
2005-08-19 0:06 ` Ciaran McCreesh
2005-08-19 1:59 ` Brian Harring
2005-08-18 15:17 ` Brian Harring
2005-08-18 15:44 ` Chris Gianelloni
2005-08-19 3:30 ` Christian Parpart
2005-08-19 3:09 ` Brian Harring
2005-08-18 17:01 ` Georgi Georgiev [this message]
2005-08-19 2:59 ` Luke-Jr
2005-08-19 5:01 ` Georgi Georgiev
2005-08-19 3:19 ` Christian Parpart
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=20050818170128.GA487528@lion.gg3.net \
--to=chutz@gg3.net \
--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