From: Brian Jackson <iggy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs
Date: Thu, 18 Aug 2005 09:27:06 -0500 [thread overview]
Message-ID: <43049ABA.4040003@gentoo.org> (raw)
In-Reply-To: <200508181628.44059.trapni@gentoo.org>
Use INSTALL_MASK to keep /usr/bin/mysqld or whatever from getting installed. We
aren't generally in the habit of splitting packages into a bunch of different
ebuilds. There are exceptions, but....
--Iggy
Christian Parpart wrote:
> Hi all,
>
> well, regarding the request on bug 88490 [1] (and my own needs) I'm in a deep
> problem ;)
>
> There *are* packages out there, that depend on (networking) client libraries
> (and their headers of course);
>
> for the general mysql ebuild, I'd propose the following splitup:
> * dev-db/mysql-server (or myssqld)
> * net-libs/libmysqlclient
> * dev-db/mysql (a meta package that simply depends on both, for backward
> compat)
>
> The reason is, that some packages need to talk to (SQL )servers, but some host
> installation do not need - or even want to (think about security policies) -
> a local (SQL) server;
>
> 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.
>
> This idea of course is applicable for lots of more packages, but mysql is one
> use case where I myself ran into;
>
> Do we have a general accepted gentoo policy for this?
>
> And... any thoughts on this subject?
>
> Regards,
> Christian Parpart.
>
> [1] http://bugs.gentoo.org/show_bug.cgi?id=88490
--
I top post... suck it
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-18 14:31 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 [this message]
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
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=43049ABA.4040003@gentoo.org \
--to=iggy@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