On Mon, Sep 09, 2002 at 06:18:44PM +0200, Goswin Brederlow wrote: > Stefano Zacchiroli <[EMAIL PROTECTED]> writes: > > > On Mon, Sep 09, 2002 at 12:15:06PM +0200, Sven LUTHER wrote: > > > > For speed reasons I also want to provide a optimised version on archs > > > > that support it. The above tests find the right (best) ocamlopt. But > > > > how do I know that there is one at all? I don't want to build a deb on > > > > archs that don't have ocamlopt. Using arch=i386,alpha,... in the > > > > control field would need a change when more archs get a ocamlopt. i > > > > would prefer a more automatic way. > > > > > > Mmm, i thought some day about having a file shipped with the ocaml > > > package that list all supported architectures, so you could simply add > > > this to the control file (with a varsubst or something such). > > > > > > But i am not entirely sure if it will work or not. > > > > > > That said, if you build depend on ocaml-native-compilers, then the > > > package will not be build on arches that don't support the native > > > compilers, but i guess this is not a solution. > > > > I suppose that this solution prevent mldonkey to enter testing because > > the build is tried on all archs but on some of them it continue failing > > due to unsatisfied build dependencies. > > Someone at #debian-devel said that it should only prevent mldonkey > from going into testing if a previous version existed. > > That might be something to check out though.
Well, another thing i didn't think of. > > The idea of shipping a file describing the supported archs + the var > > substitution seems nice to me. > > Have anyone idea of how the varsubst stuff works? > > The arch is in the dsc file and that gets copied from the control > file. I'm not sure you can use someling like the shlibs thingy for the > arch field. Mmm, effectively, this is a problem. > Another thing to check out. Yes, a better solution need to be found. But then, i am not sure it is possible with the current state of things. Friendly, Sven Luther
