All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] BogoFeeds reloaded
Date: Wed, 19 Dec 2007 13:32:08 +0200	[thread overview]
Message-ID: <1187652493.20071219133208@gmail.com> (raw)

Hello openembedded-devel,

  After the ipk deploy dirs were split to be per-arch, there was a
long discussion that people want to use deploy dir as the feed
directly as it is awfully practical, and that they are not advised to
do that due to various second-rate issues, so such usage should be
called "bogofeed".

  This month should have most of it:
http://projects.linuxtogo.org/pipermail/openembedded-devel/2007-March/thread.html#1658


  There were even patches posted, but they all were questionable as
either they tried to make per-arch vs flat layout configurable, which
could lead to behavior discrepancies in the future, or tried to do
some post-processing, like copying hundreds of megabytes around, while
the very first argument while deploy dir layout could be changed under
people's feet was that even in the case of flat layout, some
post-processing was required to get production-quality feed, and that
postprocessing can be well made outside of OE (hello Makefiles).

  Then, it all died off, with different people adopting different
solutions well suiting exactly them, as usual.

  Well, using deploy dir as feed directly is still demolishfully
practical, and clearing off my tree for NY, I'd finally want to offer
the solution I've been using since then. Unlike solutions cited, it
doesn't try to warp world to get familiar flat look, instead it
rejoices 3D and sails on it, all in 6 lines, why I think it could
finally get into.

--- classes/image.bbclass       57e9ee07875e7423b6e199df2c69e55bdcdb8a69
+++ classes/image.bbclass       a5d924355c51d4ef706a5c60d520aa4dde64d764
@@ -125,6 +125,13 @@ insert_feed_uris () {
                # insert new feed-sources
                echo "src/gz $feed_name $feed_uri" >> ${IMAGE_ROOTFS}/etc/ipkg/${feed_name}-feed.conf
        done
+
+       if [ -n "${FEED_LOCAL_BASE_URI}" ]; then
+           for arch in ${PACKAGE_ARCHS}
+           do
+               echo "src/gz local-$arch ${LOCAL_FEED_BASE_URI}/$arch" >> ${IMAGE_ROOTFS}/etc/ipkg/local-$arch-feed.conf
+           done
+       fi
 }
 
So, you set FEED_LOCAL_BASE_URI to the root of deploy dir as exported
by Apache, and - voila - you get nice collection of per-arch local feeds in
the image.


-- 
Best regards,
 Paul                          mailto:pmiscml@gmail.com




             reply	other threads:[~2007-12-19 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 11:32 Paul Sokolovsky [this message]
2007-12-19 12:20 ` [RFC] BogoFeeds reloaded Koen Kooi
2007-12-22 12:45   ` Paul Sokolovsky
2007-12-22 15:13     ` Koen Kooi
2007-12-22 16:14       ` Paul Sokolovsky
2007-12-19 13:04 ` Michael 'Mickey' Lauer
2007-12-19 13:55 ` Regno Stefano
2007-12-19 14:51   ` Koen Kooi

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=1187652493.20071219133208@gmail.com \
    --to=pmiscml@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.