public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gnome <gnome@gentoo.org>
Subject: Re: [gentoo-dev] libgphoto2-2.4.10 news item
Date: Sun, 13 Feb 2011 21:00:31 +0100	[thread overview]
Message-ID: <1297627231.7535.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20110213193440.475debea@googlemail.com>

[-- Attachment #1: Type: text/plain, Size: 816 bytes --]

On Sun, 2011-02-13 at 19:34 +0000, Ciaran McCreesh wrote:
> On Sun, 13 Feb 2011 20:31:23 +0100
> Pacho Ramos <pacho@gentoo.org> wrote:
> > Wouldn't be any shorter way to build all CAMERAS? We don't want to
> > default to enabling all, with the new way of handling this, if CAMERAS
> > is not set or is empty, nothing will be built but, if CAMERAS="*"
> > shouldn't be used, what should we use instead of having to manually
> > add all of them to make.conf (from a user point of view)
> 
> Why not specify all the CAMERAS you know about as being on by default in
> the profile? Users who care enough can override this with an explicit
> subset.
> 

If rest of gnome team agrees, I think we could go with, but I still fail
to see what is the "technical" problem on allowing CAMERAS="*" to be
used :-|

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-02-13 20:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13 17:03 [gentoo-dev] libgphoto2-2.4.10 news item Pacho Ramos
2011-02-13 17:09 ` Ciaran McCreesh
2011-02-13 17:16   ` Pacho Ramos
2011-02-13 19:31   ` Pacho Ramos
2011-02-13 19:34     ` Ciaran McCreesh
2011-02-13 20:00       ` Pacho Ramos [this message]
2011-02-13 20:17         ` Ciaran McCreesh
2011-02-14  9:07           ` [gentoo-dev] " Duncan
2011-02-14 13:17             ` Ciaran McCreesh
2011-02-14 10:35           ` [gentoo-dev] " Pacho Ramos
2011-02-14 13:21             ` Ciaran McCreesh
2011-02-13 20:00       ` Matthew Summers
2011-02-13 20:08         ` Pacho Ramos
2011-02-14 10:15 ` Pacho Ramos
2011-02-14 10:24   ` Gilles Dartiguelongue
2011-02-14 10:34     ` Pacho Ramos
2011-02-14 10:37       ` Gilles Dartiguelongue
2011-02-14 10:40         ` Pacho Ramos
2011-02-14 10:42           ` Pacho Ramos
2011-02-14 10:53             ` Gilles Dartiguelongue
2011-02-14 13:19             ` Ciaran McCreesh
2011-02-14 13:33               ` Pacho Ramos
2011-02-14 13:41                 ` Ciaran McCreesh
2011-02-14 18:25                   ` Pacho Ramos
2011-02-14 10:41   ` Ulrich Mueller
2011-02-14 10:53     ` Pacho Ramos

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=1297627231.7535.7.camel@localhost.localdomain \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gnome@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