From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] bogofeed creation
Date: Fri, 09 Mar 2007 11:12:37 +0000 [thread overview]
Message-ID: <1173438757.5864.61.camel@localhost.localdomain> (raw)
In-Reply-To: <45F13D02.9090402@whitby.id.au>
On Fri, 2007-03-09 at 21:24 +1030, Rod Whitby wrote:
> You all know what this is about, so I won't bother repeating the
> arguments for or against.
>
> Here is a proposed method of bogofeed creation.
>
> > ============================================================
> > --- packages/meta/package-index.bb 4f33564e2d11f46b7975676e5901b225190d4920
> > +++ packages/meta/package-index.bb bd6e82e439382919a03c936ef326e8de3149c27d
package-index updates the index in deploy/ipk. I propose this bogofeed
should be a new .bb file, make-bogofeed.bb or something as they do two
different things.
I don't like "rm -rf ${DEPLOY_DIR_IPK}/$d/morgue" as that's not
something this script should be doing.
Personally, I still think there should be a flag to get the old feed
behaviour back.
Cheers,
Richard
next prev parent reply other threads:[~2007-03-09 11:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 1:14 [oe-commits] org.oe.dev rootfs_ipk: as per OE, policy: remove feed management tools Andy Wilcox
2007-03-02 8:22 ` Stelios Koroneos
2007-03-02 9:25 ` Rod Whitby
2007-03-02 10:00 ` Koen Kooi
2007-03-03 17:19 ` Matthias Hentges
2007-03-03 22:47 ` Richard Purdie
2007-03-04 0:08 ` Matthias Hentges
2007-03-04 10:42 ` Richard Purdie
2007-03-02 9:47 ` Koen Kooi
2007-03-03 19:22 ` Richard Purdie
2007-03-04 8:43 ` Koen Kooi
2007-03-04 10:59 ` Richard Purdie
2007-03-04 11:31 ` Koen Kooi
2007-03-04 14:49 ` Matthias Hentges
2007-03-04 15:01 ` Koen Kooi
2007-03-04 15:10 ` Øyvind Repvik
2007-03-09 10:54 ` [RFC] bogofeed creation Rod Whitby
2007-03-09 11:12 ` Richard Purdie [this message]
2007-03-09 13:13 ` Rod Whitby
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=1173438757.5864.61.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox