public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting)
Date: Fri, 05 Apr 2013 17:27:07 -0400	[thread overview]
Message-ID: <515F41AB.7050700@gmail.com> (raw)
In-Reply-To: <515F37C8.2010307@gentoo.org>

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

On 04/05/2013 04:44 PM, Samuli Suominen wrote:
> libpng 1.6 is in portage, but temporarily without KEYWORDS, pending on
> testign and this conversion, help would be much appericiated with
> converting the tree to use automatic rebuilds for the upgrade
> 
> Because there is binary-only SLOT="1.2" of libpng, none of these are
> correct:
> 
> $ grep -r 'media-libs/libpng.*:=' */*/*.ebuild
> app-misc/tracker/tracker-0.14.4.ebuild:    >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.14.5.ebuild:    >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-0.16.0.ebuild:    >=media-libs/libpng-1.2:=
> app-misc/tracker/tracker-9999.ebuild:    >=media-libs/libpng-1.2:=
> media-gfx/digikam/digikam-3.0.0.ebuild:    media-libs/libpng:=
> media-gfx/digikam/digikam-3.1.0.ebuild:    media-libs/libpng:=
> media-plugins/gst-plugins-gl/gst-plugins-gl-0.10.3.ebuild:
>>=media-libs/libpng-1.4:=
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.5.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
> 
> media-plugins/gst-plugins-libpng/gst-plugins-libpng-1.0.6.ebuild:RDEPEND=">=media-libs/libpng-1.4:="
> 
> www-client/chromium/chromium-27.0.1453.12.ebuild:    media-libs/libpng:=
> www-client/chromium/chromium-27.0.1453.3.ebuild:    media-libs/libpng:=
> www-client/chromium/chromium-9999-r1.ebuild:    media-libs/libpng:=
> 
> They should all be :0= to avoid matching the :1.2 SLOT.
> 
> Plus some hundreds are completely without subslotting:
> 
> $ grep -r 'media-libs/libpng' */*/*.ebuild |grep -v ':.*='
> output -> http://bpaste.net/show/89268/
> 
> Thanks,
> Samuli
> 

I'd love to help, but I haven't done much at all with ebuild munging. If
there's a list of basic translation instructions that would work for
most ebuilds, I could certainly knock off a few.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

  parent reply	other threads:[~2013-04-05 21:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 20:44 [gentoo-dev] libpng 1.6 upgrade and subslotting (and misuse of subslotting when there is also normal slotting) Samuli Suominen
2013-04-05 21:17 ` Pacho Ramos
2013-04-05 21:22   ` Ian Stakenvicius
2013-04-05 21:43   ` Samuli Suominen
2013-04-05 21:44   ` Samuli Suominen
2013-04-05 21:27 ` Michael Mol [this message]
2013-04-05 21:46 ` Mike Gilbert
2013-04-06  1:52 ` Ben de Groot
2013-04-06  2:18   ` Ian Stakenvicius
2013-04-06 14:33     ` Alexis Ballier
2013-04-06 15:02       ` Mike Gilbert
2013-04-06 15:09         ` Alexis Ballier
2013-04-06 15:13           ` Mike Gilbert
2013-04-06 15:27             ` Ciaran McCreesh
2013-04-06 15:36               ` Alexis Ballier
2013-04-08  0:34               ` Ian Stakenvicius
2013-04-08  0:06       ` Ian Stakenvicius
2013-04-06  3:24 ` Alexandre Rostovtsev
2013-04-09  7:27 ` Sergey Popov

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=515F41AB.7050700@gmail.com \
    --to=mikemol@gmail.com \
    --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