From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] duplicate recipes
Date: Thu, 11 Mar 2010 06:10:47 +0100 [thread overview]
Message-ID: <20100311051047.GP31945@jama> (raw)
In-Reply-To: <ac9c93b11003101229s6a23a40ayb0ba2f220369086a@mail.gmail.com>
On Wed, Mar 10, 2010 at 09:29:27PM +0100, Frans Meulenbroeks wrote:
> 2010/3/10 Martin Jansa <martin.jansa@gmail.com>:
> > On Wed, Mar 10, 2010 at 04:44:48PM +0100, Frans Meulenbroeks wrote:
> >> Time for a summary I guess:
> >>
> >> original proposal from me:
> >> Probably the best scenario is to remove all versions which
> >> - are not the latest version
> >> - are not pinned with PREFERRED_VERSION in conf/distro/*
> >> - do not have the largest DEFAULT_PREFERENCE
> >
> > I think this rules are quite strict, in first iteration would be enough
> > to keep only latest from each "major" version
> >
> > where major version is defined by common-sense (ie first 2 version
> > number for xorg, but somewhere first number is enough)
> >
> > ie for xserver-xorg:
> > ../dev/recipes/xorg-xserver/xserver-xorg_1.2.0.bb
> > ../dev/recipes/xorg-xserver/xserver-xorg_1.3.0.0.bb
> > ../dev/recipes/xorg-xserver/xserver-xorg_1.4.2.bb
> > mv ../dev/recipes/xorg-xserver/xserver-xorg_1.4.bb
> > mv ../dev/recipes/xorg-xserver/xserver-xorg_1.5.1.bb
> > ../dev/recipes/xorg-xserver/xserver-xorg_1.5.3.bb
> > mv ../dev/recipes/xorg-xserver/xserver-xorg_1.7.1.bb
> > ../dev/recipes/xorg-xserver/xserver-xorg_1.7.4.bb
> >
> > and update preferred-xorg-versions (1.7.1->1.7.4) and other if needed
> >
> >> opinions:
> >
> > JaMa: move older minor versions to obsolete, keep latest for each "major"
>
> Noted!
>
> (but for my understanding:why do you see it useful to retain old
> versions that are not pinned. For xorg, being a complicated and big
> thing I can partly understand it, but is there really a point in
Yes that's where I expect it could be difficult for some machine
maintainer to jump from ie xserver-xorg-1.4.bb directly to 1.7.4, but
moving to 1.4.2 should be quite painless.
But I expect that that even removing some minor version of not so important
xorg-app can create a bit work, as new one will need ie newer
util-macros and newer util-macros maybe won't work with so old xserver
etc.
> keeping old versions of e.g. transmission? (noting that if needed they
> can always be recovered from git).
There is only one major version of transmission for me 1.x, so there
would be only one latest.
In most places it would be best to ask package maintainer / person who
added most versions to do a cleanup or send him cleaning patch for ack.
There is at least of latest versions with D_P -1 (and enabled for some
distro) where is maybe D_P not needed anymore and can be removed.
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-03-11 5:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 20:01 [RFC] duplicate recipes Frans Meulenbroeks
2010-02-28 20:06 ` Koen Kooi
2010-02-28 21:37 ` Michael 'Mickey' Lauer
2010-02-28 21:48 ` Philip Balister
2010-02-28 22:10 ` Graeme Gregory
2010-03-01 7:28 ` Frans Meulenbroeks
2010-03-10 15:44 ` Frans Meulenbroeks
2010-03-10 16:01 ` Martin Jansa
2010-03-10 20:29 ` Frans Meulenbroeks
2010-03-11 5:10 ` Martin Jansa [this message]
2010-03-10 22:06 ` Graham Gower
2010-03-11 20:13 ` Tom Rini
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=20100311051047.GP31945@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.