> > 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.
> > 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 :) > > 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. 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. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
