On Sat, 26 Apr 2008, Oliver Ertl wrote:
> > > I always compile trunk by myself and put the package repository
> > > on a web or FTP server.
> >
> > so you simply do an all-package build and create your own repo, is
> > that what you're saying? that's the direction i'm going in as
> > well.
> Yes. But I only compile the packages I need. Nothing more.
sure, but nothing stops you from just building them all just to play
it safe.
> > > In the build-system I change either
> > > package/base-files/files/etc/ipkg.conf to have a new standard
> > > ipkg.conf for all targets.
> >
> > what do you mean you change "either"? i'm assuming that what
> > you're referring to is that, before an image build, you modify the
> > contents of the generic /etc/ipkg.conf file to refer to your
> > repository, correct? and that modified version will be used for
> > any new image you build.
> Absolutly right :)
i did a quick "find" for all ipkg.conf files in a clean tree, and what
i got was:
$ find . -name ipkg.conf
./package/base-files/files/etc/ipkg.conf
./target/linux/etrax/base-files/etc/ipkg.conf
./target/linux/at91/base-files/etc/ipkg.conf
$
so i'm assuming that all image builds will use whatever is in that
first one, but etrax and at91 are the sole exceptions to that rule.
i'd never noticed that before.
> > > For target specific ipkg.conf files change or add the file
> > > target/linux/<arch>/base-files/etc/ipkg.conf.
> >
> > and i haven't looked closely enough yet -- if you have both a
> > generic and an arch-specific ipkg.conf file, what happens? are
> > the combined in your final image? a pointer to the part of the
> > build infrastructure that deals with that would be great so i can
> > RTFS for myself. thanks muchly.
> A arch specific ipkg.conf will simply overwrite the generic one.
right, as i noted above.
> You can check the contents of your final /etc/ipkg.conf file which
> goes into the image at build_dir/<arch>/root-<board>/etc/ipkg.conf
>
> I hope this helps. Sorry, my native language is German.
no problem, thanks for clearing that up.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
_______________________________________________
openwrt-devel mailing list
[email protected]
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
