Skip to contentSkip to conversation

BogoFeeds reloaded

RFC In review Paul Sokolovsky 4 participants 8 messages Dec 19, 2007 – Dec 22, 2007

lore
Share & tools
lore

Paul Sokolovsky

author
#0 lore raw

RFC 1/1 BogoFeeds reloaded

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.

image.bbclass a5d924355c51d4ef706a5c60d520aa4dde64d764 renamed from image.bbclass 57e9ee07875e7423b6e199df2c69e55bdcdb8a69 +7 -0
@@ -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.

Signature · 2 lines
Best regards,
 Paul                          mailto:[email protected]
#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Sokolovsky schreef:

Quoted 24 lines

Hello openembedded-devel,

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.

image.bbclass a5d924355c51d4ef706a5c60d520aa4dde64d764 renamed from image.bbclass 57e9ee07875e7423b6e199df2c69e55bdcdb8a69 +7 -0
@@ -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
 }
Quoted 3 lines

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.

Could you add a comment in image.bbclass and local.conf.sample on how to use this, since it looks quite the same as FEED_URI to a new user, but is quite different? And while you are at it, update the OE usermanual as well?

regards,

Koen

- --
[email protected] will go go away in december 2007, please use [email protected] instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHaQyKMkyGM64RGpERAl5PAJ49efwK4trM3EzqYexrczg1zb9nzACeP9Zk HMWnYe+hVkyVCtks4K7b62o=
=j0vG
-----END PGP SIGNATURE-----

author
#2 lore raw

Hello Koen,

Wednesday, December 19, 2007, 2:20:26 PM, you wrote:

[]

Quoted 9 lines
Quoted 9 lines
image.bbclass a5d924355c51d4ef706a5c60d520aa4dde64d764 renamed from image.bbclass 57e9ee07875e7423b6e199df2c69e55bdcdb8a69 +7 -0
+
+       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
 }
Quoted 8 lines
Quoted 3 lines

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.

Could you add a comment in image.bbclass and local.conf.sample on how to use this, since it looks quite the same as FEED_URI to a new user, but is quite different? And while you are at it, update the OE usermanual as well?

Ok, to make it more precise, I've renamed it to
FEED_DEPLOYDIR_BASE_URI. Added comments here and there.

Edited also the manual, it lacked and FEED_* description at all, so
I've added section on it. I also rearranged chapters in manual so it was more natural to learning reader: Intro - Getting Started - everything else. Now, questions about manual availability. Is
http://www.openembedded.org/user-manual updated anyhow? It lacks changes I made ~week ago to describe ASSUME_SHLIBS. There's no mentioning of PDF manual on OE site, instead, there's news somewhere deep on Angstrom site. And http://www.openembedded.org/%7Ekoen/usermanual.pdf
it links to dated 2007-10-09.

Quoted 3 lines

regards,

Koen

Signature · 2 lines
Best regards,
 Paul                            mailto:[email protected]
#3 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Sokolovsky schreef:

Quoted 24 lines

Hello Koen,

Wednesday, December 19, 2007, 2:20:26 PM, you wrote:

[]

Quoted 9 lines
Quoted 9 lines
image.bbclass a5d924355c51d4ef706a5c60d520aa4dde64d764 renamed from image.bbclass 57e9ee07875e7423b6e199df2c69e55bdcdb8a69 +7 -0
+
+       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
 }
Quoted 8 lines
Quoted 3 lines

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.

Could you add a comment in image.bbclass and local.conf.sample on how to use this, since it looks quite the same as FEED_URI to a new user, but is quite different? And while you are at it, update the OE usermanual as well?

Quoted 8 lines

Ok, to make it more precise, I've renamed it to
FEED_DEPLOYDIR_BASE_URI. Added comments here and there.

Edited also the manual, it lacked and FEED_* description at all, so
I've added section on it. I also rearranged chapters in manual so it was more natural to learning reader: Intro - Getting Started - everything else. Now, questions about manual availability. Is
http://www.openembedded.org/user-manual updated anyhow?

It's being updated hourly for the org.openembedded.documentation branch on monotone.openembedded.org

Quoted 2 lines

It lacks
changes I made ~week ago to describe ASSUME_SHLIBS.

Those changes aren't in the db on monotone.openembedded.org, did you do 'mtn sync monotone.openembedded.org org.openembedded.{dev,documentation}' ?

Quoted 4 lines

There's no
mentioning of PDF manual on OE site, instead, there's news somewhere deep on Angstrom site. And http://www.openembedded.org/%7Ekoen/usermanual.pdf
it links to dated 2007-10-09.

'make pdf' was having some troubles, so it is html only for the time being. The angstrom folks provide a pdf version out of courtesy.

Quoted 3 lines
Quoted 3 lines

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHbSmBMkyGM64RGpERArVlAKCl7W1FbXIAcPqS9oqPRkymERoj8wCbBzI0 SzOYn81Te9KjtCOZ8WKivso=
=17yP
-----END PGP SIGNATURE-----

author
#4 lore raw

Hello Koen,

Saturday, December 22, 2007, 5:13:06 PM, you wrote:

[]

Quoted 6 lines
Quoted 2 lines

It lacks
changes I made ~week ago to describe ASSUME_SHLIBS.

Those changes aren't in the db on monotone.openembedded.org, did you do 'mtn sync monotone.openembedded.org org.openembedded.{dev,documentation}' ?

Oh yeah, I already figured what was wrong ;-\. Now re-merging my
changes...

[]

Signature · 2 lines
Best regards,
 Paul                            mailto:[email protected]
#5 lore raw
In reply to Paul Sokolovsky
Quoted 3 lines · Paul Sokolovsky

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.

Excellent. A nice, non-invasive, utterly practical solution.

I like it.

Regards,

:M:

Signature · 1 line
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
#6 lore raw
In reply to Paul Sokolovsky

I found the package about VNC but i have this error bitbake x11vnc_0.9.3.bb
ERROR: Unable to parse conf/bitbake.conf (Could not inherit file classes/autotools.bbclass)

What can i do to solve thet, i must unpack it and compile for arm MX31

#7 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Regno Stefano schreef:

Quoted 5 lines

I found the package about VNC but i have this error bitbake x11vnc_0.9.3.bb
ERROR: Unable to parse conf/bitbake.conf (Could not inherit file classes/autotools.bbclass)

What can i do to solve thet, i must unpack it and compile for arm MX31

Hello mister thread-hijacker. Bye.

- --
[email protected] will go go away in december 2007, please use [email protected] instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHaTAAMkyGM64RGpERAsKgAKClYw+IYaI+yOHethPm10Uj2VxTNgCgmuF4 imLQw7RYM6nxsFU1IN293Rw=
=tOja
-----END PGP SIGNATURE-----