From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] openssl: update 1.0.0 to 1.0.0a
Date: Tue, 17 Aug 2010 09:05:48 +0200 [thread overview]
Message-ID: <20100817070548.GD11569@jama> (raw)
In-Reply-To: <201008171050.16611.roman@khimov.ru>
On Tue, Aug 17, 2010 at 10:50:13AM +0400, Roman I Khimov wrote:
> В сообщении от Понедельник 16 августа 2010 23:35:59 автор Khem Raj написал:
> > IMO the newest version in a recipe should always be default preference
> > this way we can
> > stabilize recipe upgrades quicker. This also means a wider testing
> > before pushing a new recipe
> > DEFAULT_PREFERENCE = "-1" makes it to escape the testing.
>
> Well, consider Perl, for example. Making 5.10.1 a default preference would
> break binary packaged perl modules built for 5.8.8, so technically some
> massive PR bump (most probably DISTRO_PR) is needed when updating to 5.10.1.
> Forcing distro maintainers to do that is not nice, IMO.
But if you drop D_P globally you can bump PR of depending packages just
once. If distro maintainders add P_V_perl = "5.10.1" one by one, then we'll have
multiple PR bumps.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-08-17 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 18:36 [PATCH] openssl: update 1.0.0 to 1.0.0a Roman I Khimov
2010-08-16 18:59 ` Frans Meulenbroeks
2010-08-16 19:25 ` Roman I Khimov
2010-08-16 19:32 ` Frans Meulenbroeks
2010-08-16 19:35 ` Khem Raj
2010-08-16 20:10 ` Frans Meulenbroeks
2010-08-17 6:50 ` Roman I Khimov
2010-08-17 7:05 ` Martin Jansa [this message]
2010-08-17 7:06 ` Frans Meulenbroeks
2010-08-17 7:26 ` `DEFAULT_PREFERENCE = "-1"` of current (upstream) releases (was: [PATCH] openssl: update 1.0.0 to 1.0.0a) Paul Menzel
2010-08-17 8:42 ` Dr. Michael Lauer
2010-08-17 11:58 ` [PATCH] openssl: update 1.0.0 to 1.0.0a Martin Jansa
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=20100817070548.GD11569@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.