I'm trying to understand hot to configure opk in order, when the
system will be in run, to install opkg packages from my pc.
By now I succeded modifying the rootfs like this
I'm trying to understand hot to configure opk in order, when the
system will be in run, to install opkg packages from my pc.
By now I succeded modifying the rootfs like this
I did something similar last week and had the following problems
I copied the oe/tmp/deploy/glibc/ipk directory as a hole and expected
that pointing to that would work.
I did not because the Package and Packages.gz in that directory are
empty (on my install)
I had to add the different sub dirs separately
The package was build into oe but was not in the Packages and
Pacakges.gz (this is was appareently
not done automatically)
I had to run bitbake package-index to update the Packages.gz
I expected that searching for a package would work :opkg seach gcc
This did not work you have a provide an expression that matches the
whole package so
opkg search "*gcc*" worked
I have no network so i "simply" copied the ipk directory to the mmc
and created a new feed
root@beagleboard:~# cat /etc/ipkg/aaa-feed.conf
src/gz local-all file:///ipk/all
src/gz local-arm file:///ipk/armv7a
src/gz local-beagle file:///ipk/beagleboard
Hope this help, I wand to add this info to the elinux wiki
But I think is not necessary to copy to mmc, but for example I have
installed, on my pc, apache2, and made a link, on my pc,
like this:
ls -al /var/www/IPK
lrwxrwxrwx 1 root root 68 2009-03-07 01:29 /var/www/IPK -> /media/
discone-100GB-resiserfs/oe_stable/tmp/deploy/glibc/ipk
I have to try.
The thing the I really didn't know was to do 'bitbake package-
index' .
This shoulb solve my problem reabuilding the index with know
compilations.
Answer these questions:
* Which other kernel is used on the beagleboard?
* Which other DSP is used on the beagleboard?
* Which other SD card driver is used on the beagleboard?
Then you would realize that a question asked for any of these is
pertinent for *any* beagleboard user. The slightly more dubious one is
toolchains, but one can switch toolchains rather easily, so seeing a
question answered for another toolchain (not the one you use) can be
actually useful for you too.
However, distribution-specific questions are completely different. Are
we expected to have questions answered for Fedora, Debian, Maemo,
Ubuntu, Moblin, ALIP, and any other distribution-kind of software?
WTF are you talking about? Those are *examples*, more specifically;
examples of distributions that I thought *you* were not interested in
discussing on the beagleboard mailing list, therefore strengthening my
point.
Do you need some kind of validation? Then + Angstrom, Poky Linux,
OpenEmbedded, Open Moko... stuff I'm not familiar with, I'm not even
sure they are distributions, and I don't really care.
I'm OK with announcements like: "new online image builder for
Angstrom", that's interesting for *all* beagleboard users. But "how do
I fix my opkg", sorry, that's spam... what is opkg and why should *I*
(a beagleboard user) care?
I'm trying to understand hot to configure opk in order, when the
system will be in run, to install opkg packages from my pc.
By now I succeded modifying the rootfs like this
This is *not* a question for the beagleboard mailing list.
I do appreciate what you are trying to do (define what the topic of
the list is). In my interpretation
anything that runs on beagle,promotes using the omap35xx, make
companies produce specs and or open source
is currently ON topic. BSD would be and also talks about WinCE and
android, the linux kernel, uboot.
Overall the tone on the mailing list is very good. We can try to point
people to external content or suggest to
ask the question elsewhere but "This is *not* a question for the
beagleboard mailing list" is a bit hard
I can say the same for android mails, but I don't complain about them, since this is a community with diverse interests. I think it would be anti-social to force everyone to use the 'proper' mailinglist for questions that aren't strictly beagleboard related. Some of these people are new to open-source and linux and don't know which mailinglist to use yet. Your elitist attitude is scaring them off.
So instead of signalling the problems you should offer solutions. For example:
Note that I've said I don't know know much about opkg, bitbake, OE, or
any of that stuff, so how am I supposed to do "Good" or "Better"?
Since no one is doing "Good" or "Better" I was forced to do "Bad".
It looks like I'll have to learn a bit more about this stuff to give
proper redirection.
Anyway,
I'm sorry for the situation.
In my opinion everything can make a beagleboard work is positive for
Ti: if I can install packages without rebuilding all is really
important beacuse it saves time.
I'll not put CE in all my life (I hope) on beagleboard, but for Ti
also this is interesting.
Officially I don't know if I should worry about Felipe Contreras
opinion because I don't find a precise set of rules, I have only found
the description of this group, that is "Low-cost, fan-less, ARM-based
computer user's group".
Anyway my purpose is not to create spam and so I will try to
understand who is the responsible of http://groups.google.com/group/beagleboard
before posting something that will not be about the hardware of
beagleboard.
Remember that limiting the freedom, and sometimes the spam, is not a
good thing for the development.
I'm not blaming you. I think we should come up with better guidelines
for this mailing list. I don't think there's any guideline right now,
and so far it was worked pretty well. But at least to me this OE stuff
is starting to get annoying.
I agree that limiting the freedom might have bad consequences, but the
same would happen if there were no limits at all.
When you are subscribed to dozens of mailings lists, you really want
them to stay on-topic.
Would it? The solution was to do "bitbake package-index", it seems
there's a separate mailing list for bitbake. So is it opkg, or
bitbake, or is it OE, or something else?
Sure, I could have googled and pointed to a mailing list, and there
were pretty high chances that it would be the wrong mailing list.
The only thing I know, is that it doesn't belong to the beagleboard
mailing list, and I want to improve the mailing list, so I was forced
to do something suboptimal.
And BTW, Good: assume people have good faith, Bad: call people names
like asshat.
There are very many "newbie" users on this mailing list. If you would like me to step in and define a policy, I can do so, but my preference is to be as open as possible and let these things work themselves out. I believe we are very close to that point if we can allow this topic to now die.
There tends to be a lot of distribution-specific questions here and I believe that is important to help people get started. When they become very distribution-specific and not BeagleBoard-specific, they should be politely redirected to appropriate mailing lists. To aide people in finding out about the various distributions and where they collaborate, I've created a FAQ entry: http://elinux.org/BeagleBoardFAQ#Linux_Distributions. There are advantages to us all knowing a little bit about each.