public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: Gilles Dartiguelongue <eva@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, pr@gentoo.org, gnome <gnome@gentoo.org>
Subject: Re: [gentoo-dev] libgphoto2-2.4.10 news item
Date: Mon, 14 Feb 2011 11:34:02 +0100	[thread overview]
Message-ID: <1297679642.7123.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1297679073.16086.3.camel@gdartigu.lan.rep.sj>

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

El lun, 14-02-2011 a las 11:24 +0100, Gilles Dartiguelongue escribió:
> Le lundi 14 février 2011 à 11:15 +0100, Pacho Ramos a écrit :
> > El dom, 13-02-2011 a las 18:03 +0100, Pacho Ramos escribió:
> > > Hello
> > > 
> > > Please see attached news item for reviewing as part of the fix for
> > > http://bugs.gentoo.org/show_bug.cgi?id=346491
> > > 
> > > Thanks
> > > 
> > 
> > This is an updated news item for trying to cover Ciaran and Matthew
> > suggestions:
> > 1. It doesn't ask people to use USE="*"
> > 2. Before sending this, I would add all cameras to base/make.defaults as
> > already done for similar cases (like alsa, lcd devices and others)
> > 
> > Do you agree with this?
> > 
> > Thanks :-)
> 
> no, adding all cameras is most likely a waste of time for maintainers,
> it is prone to errors when cameras get added/removed which is already
> complicated enough to maintain.
> 

What kind of errors will people see? As I have just tested, if I run:
 CAMERAS="bbhsgdd" emerge -pv media-libs/libgphoto2

I get no error (that would be equivalent to a camera that got removed on
a bump). 

In the case of a CAMERA addition, we would see it when bumping (as one
of them wouldn't be enabled automatically). It doesn't look to
complicate to maintain for me then :-/

> If someone really wants a non-null default, I suggest enabling the ptp2
> camera driver (PTP support) which is available for most cameras out
> there.
> 



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

  reply	other threads:[~2011-02-14 10:34 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
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 [this message]
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=1297679642.7123.8.camel@localhost.localdomain \
    --to=pacho@gentoo.org \
    --cc=eva@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gnome@gentoo.org \
    --cc=pr@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