On Sat, 11 Jun 2011 23:39:49 +0200 Yann Dirson <ydir...@free.fr> wrote:
> It looks like my problem is about understanding what the files > provided by multistrap are all about. Read the manpage. It gives an example config for a simple root filesystem and gives the filename of the conf script which is named lenny.conf That should have given you a clue that you select root filesystem configuration files according to the suite you want to use. Select cross-building chroot conf files according to the architecture for which you want to build. If you find that non-obvious, document it on the Wiki which also has lots more examples, again using the suite as the divisor. http://wiki.debian.org/Multistrap This wiki page is also described in the manpage. This bug will remain closed and I'm not going to add spurious comments to the various scripts. There is a lot of documentation out there and it is all linked from the manpage which is always the first point of call for help with a Debian package. *Not* bug reports. > OK. Then a note about its purpose would be welcome, say at the > beginning of the script. "meant to be called from multistrap with > directory arch variables" does not really help in ths respect. If the reference IN THE FILE to pdebuild-cross didn't help, I don't see the point. > Indeed, my goal being to build an armel device rootfs, I naively > selected "armel.conf" as a starting point. The example in the manpage clearly links to lenny.conf and indicates that the conf file is independent of the architecture of the packages to use for the rootfs. The armel.conf file itself references crosschroot.conf! > Indeed, armel.conf includes crosschroot.conf, and the contents of that > one should again have helped me. Yes, it really should. > But maybe renaming it to something > like "crossbuildchroot.conf" would be more accurate, and better guide > the poor soul trying to make sense of all this late at night :) This file is referenced by dozens of build systems which are separate from Debian. There is no reason to break these systems when the documentation already exists - it's not a bug in the package if you didn't read the docs. Late at night is not an excuse. > > It is provided to assist pdebuild-cross. > > So why isn't it shipped with pdebuild-cross instead ? It is the multistrap conf file which pdebuild-cross uses. pdebuild-cross only needs it to setup the chroot the first time and only uses by calling multistrap. > Right. It looks like my problem was just that I expected a conf file > suitable for the third case, and having selected a wrong one I did not > adapt it correctly. In fact, it looks like there is no conf file > shipped for this case, or did I just miss it ? There is one for each commonly used suite already packaged in /usr/share/multistrap. Any of those can be used for any architecture for which you can find a repository. lenny.conf, squeeze.conf, wheezy.conf, sid.conf... > Anyway, improving the > naming of those files would help users to quickly and acurately select > the one they need. The architecture of the rootfs has nothing to do with the rest of the content of the file as it can be overridden on the command line, so there is no need to rename any files. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
pgpBI43Vrm09D.pgp
Description: PGP signature
