public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, pr@gentoo.org,
	gnome <gnome@gentoo.org>,  Gilles Dartiguelongue <eva@gentoo.org>
Subject: Re: [gentoo-dev] libgphoto2-2.4.10 news item
Date: Mon, 14 Feb 2011 11:53:19 +0100	[thread overview]
Message-ID: <1297680799.7123.13.camel@localhost.localdomain> (raw)
In-Reply-To: <19801.1763.90079.647999@a1i15.kph.uni-mainz.de>


[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]

El lun, 14-02-2011 a las 11:41 +0100, Ulrich Mueller escribió:
> >>>>> On Mon, 14 Feb 2011, Pacho Ramos wrote:
> 
> > Title: Change on CAMERAS handling in libgphoto2-2.4.10
> 
> Too long. GLEP 42 allows a maximum of 44 characters for the title.
> 
> > In order to not violate package manager handling (http://bugs.gentoo.org/346491),
> > selective cameras build logic has been modified in libgphoto2-2.4.10 to build all
> > by default, nothing if CAMERAS variable is set to an empty value and only the ones
> > specified otherwise.
> 
> "The text body should be wrapped at 72 characters" says GLEP 42.
> 
> Ulrich
> 

This should fix these issues. Also tells ptp2 is the default as talked
here because it looks like the best option. 

OK with this?

[-- Attachment #1.2: 2011-02-14-libgphoto-2.4.10.en.txt --]
[-- Type: text/plain, Size: 522 bytes --]

Title: Change on CAMERAS in libgphoto2-2.4.10
Author: Pacho Ramos <pacho@gentoo.org>
Content-Type: text/plain
Posted: 2011-02-14
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <media-libs/libgphoto2-2.4.10

In order to not violate package manager handling, selective cameras 
build logic has been modified in libgphoto2-2.4.10 to build 'ptp2' by 
default, nothing if CAMERAS variable is set to an empty value and only 
the ones specified otherwise.

See http://bugs.gentoo.org/346491 for reference.

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

      reply	other threads:[~2011-02-14 10:54 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
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 [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=1297680799.7123.13.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 \
    --cc=ulm@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