Community,

I'm currently cooking Piranha 2 and I have some open questions regarding buildroot:

1. One can place custom files (e.g. scripts) into trunk/files/usr/bin to appear in the jffs2 at /usr/bin. I'm wondering if the execution flags will be preserved in the jffs2 if I chmod 755 a certain script in trunk/files subdirectory.

2. Let's assume I'd like to setup a custom repository with some ipks. Let's assume stock OpenWrt provides aircrack-ng r1142 in the official 8.09 repo and I put, let's say, r1396 into my custom repo at klashed.net and define both repos in a custom /etc/opkg.conf. Is opkg smart enough to install the higher revision from klashed.net if I issue opkg install aircrack-ng? I.e. does it install r1396 instead of r1142 automatically due to the higher revision number as apt-get would do?

3. Another opkg related thing: Let's assume I have a certain Makefile and I define some depends in there. Furthermore I define not to introduce the resulting ipks (the tool + dependencies) into the jffs2 but to build them as plain ipks. Now, let's assume I put these ipks into a repo, define this in /etc/opkg.conf and issue opkg install somepackage. Does opkg resolve the dependencies I defined in the Makefile automatically? I mean does it install e.g. libpthread when installing aircrack-ng? I know opkg has this capaility but I'm wondering if the depend definition in the Makefile is enough for opkg to know that a certain package depends on something else.

4. Is there a smart way to introduce an already compiled ipk to the jffs2 using buildroot? I mean, let's assume I don't have the sources for that ipk and/or no Makefile is available but the compiled ipk. Is there a smarter way then extracting the ipk and place everthing inside the tarball in subdirectories of trunk/files?

There's certainly some more to come, but that's what I'm wondering about currently.

Thanks in advance for your support,
orange

One more thing:

5. Let's assume I have a set of scripts, I put them into trunk/files subdirectories for the inclusion into the jffs2. Now let's assume these scripts needs a bunch of dependencies for proper operation out of OpenWrt's package tree and I'd like to avoid to select them all manually in make menuconfig. If the set of scripts would be based on some sources available somewhere I could write a Makefile for them and introduce all dependencies in there - problem solved, BUT... what if these scripts itself do not require any compilation at all? Does buildroot support kinda "metapackages" that just takes care of dependency resolution?

best,
orange