From: Francesco R <vivo@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 17:28:24 +0200 [thread overview]
Message-ID: <4304A918.6080703@gentoo.org> (raw)
In-Reply-To: <4304A59D.8050901@gentoo.org>
Lance Albertson wrote:
>Mike Frysinger wrote:
>
>
>>On Thursday 18 August 2005 10:28 am, Christian Parpart wrote:
>>
>>
>>
>>>Do we have a general accepted gentoo policy for this?
>>>
>>>
>>general policy is to not split packages (and i agree with this ...)
>>
>>
>
>bind and bind-tools is split ;) Why is it so bad to split packages? (I'm
>just curious) Seems a bit odd that we can't have a library only, client
>only, etc package like the other distros. Of course, I understand that
>we could use useflags for that, but is that really the best solution for
> this particular issue?
>
>Oh well, I'm just a sysadmin, not a coder so I'll got back to my cave. ;)
>
>
>
vimdiff bind-tools/bind-tools-9.2.5.ebuild bind/bind-9.2.5-r5.ebuild
In the eventuality of mysql being splitted the landscape is totally
different.
The code to duplicate is a 40% of the ebuild speaking of volume, in
maintenance the percentage is bigger.
I'm a (little) sysadmin too, redundancy is good speaking of servers but
maintain a cluster or simply to synced servers is more difficult (and
error prone) that maintain only one, right ?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-18 15:52 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 [this message]
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=4304A918.6080703@gentoo.org \
--to=vivo@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