public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gilles Dartiguelongue <eva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] client/server consistency: USE flags / split packages
Date: Tue, 10 Nov 2009 01:50:07 +0100	[thread overview]
Message-ID: <57CD634A-0CD7-42DB-822A-ADEF9EC62DCD@gentoo.org> (raw)
In-Reply-To: <1257362741.20584.2322.camel@tablet>


Le 4 nov. 2009 à 20:25, Peter Volkov a écrit :

> В Срд, 04/11/2009 в 17:34 +0100, Tiziano Müller пишет:
>> Am Mittwoch, den 04.11.2009, 18:44 +0300 schrieb Peter Volkov:
>>> So are there any good reasons to split packages?
>>
>> In environments with a staging server and binary packages, yes.

in case where different libs are needed in the stack but in ways that  
makes it do circular deps if you use an unsplitted package (think  
gvfs, libsoup, libproxy libsoup, and stuff like that).

I think it's generally a good idea to split when the following  
conditions are met:
  * maintainer/herd has enough time to maintain the split (some splits  
can be time consuming)
  * upstream behaves nicely in the split case (splitting stuff on our  
own is shooting ourselves in the feet usually as is upstream not  
wanting to hear about it)
  * split benefits the user has it allows more flexibility (don't tell  
me about configure times, we are gentoo and flexibility most often  
wins over buildtime or we'd be somewhere else imho)

-- 
Gilles Dartiguelongue <eva@gentoo.org>
Gnome team






      reply	other threads:[~2009-11-10  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 15:44 [gentoo-dev] client/server consistency: USE flags / split packages Peter Volkov
2009-11-04 16:28 ` Petteri Räty
2009-11-15 14:21   ` Jorge Manuel B. S. Vicetto
2009-11-04 16:34 ` Tiziano Müller
2009-11-04 19:25   ` Peter Volkov
2009-11-10  0:50     ` Gilles Dartiguelongue [this message]

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=57CD634A-0CD7-42DB-822A-ADEF9EC62DCD@gentoo.org \
    --to=eva@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