public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] client/server consistency: USE flags / split packages
Date: Wed, 04 Nov 2009 22:25:41 +0300	[thread overview]
Message-ID: <1257362741.20584.2322.camel@tablet> (raw)
In-Reply-To: <1257352489.6780.433.camel@localhost>

В Срд, 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.

Currently you either have to script your staging server correctly (play
with PKGDIR) or use different build hosts for different configurations.
In any way, this does not justify pushing USE flags into package names.

-- 
Peter.




  reply	other threads:[~2009-11-04 19:26 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 [this message]
2009-11-10  0:50     ` Gilles Dartiguelongue

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=1257362741.20584.2322.camel@tablet \
    --to=pva@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