Hello, On Mon, May 12, 2014 at 08:27:46PM +0200, Lucas Satabin wrote: > Hi Martin > > On 10/05/2014 23:08, Martin Quinson wrote: > > > > the bootstraping process in Scala is very far from packager-friendly. > > > >and here are the ones of 2.11 (from Lucas's current git) > >(obtained by running >>cat `find -name "*desired.sha1"`<< from root dir) > > > >e737b123d31eede5594ceda07caafed1673ec472 *code.jar -> same as 2.9 > >1b11ac773055c1e942c6b5eb4aabdf02292a7194 ?instrumented.jar -> new version > >981392dbd1f727b152cd1c908c5fce60ad9d07f7 *enums.jar -> same > >cd33e0a0ea249eb42363a2f8ba531186345ff68c *nest.jar -> same > >346d3dff4088839d6b4d163efa2892124039d216 ?jsoup-1.3.1.jar -> 1.7.3 is > >already packaged > >02fe2ed93766323a13f22c7a7e2ecdcd84259b6c *annotations.jar -> same > >be8454d5e7751b063ade201c225dcedefd252775 *methvsfield.jar -> same > >3794ec22d9b27f2b179bd34e9b46db771b934ec3 ?macro210.jar -> new thing > >b1ec8a095cec4902b3609d74d274c04365c59c04 *genericNest.jar -> same > >0392ecdeb306263c471ce51fa368223388b82b61 ?jsr166_and_extra.jar -> same > >ddd7d5398733c4fbbb8355c049e258d47af636cf ?forkjoin.jar -> new version > >a1883f4304d5aa65e1f6ee6aad5900c62dd81079 ?push.jar -> same > > > > I started to look how to make the build work without downloading anything. > Several dependencies are used to runs tests or to publish new jars, I think > we can cut them off for now. > I already did it for some of them but I need to finish this and test it more > thoroughly. > To bootstrap the all stuff, maybe we need to momentarily commit some jars > into the git repository.
What about removing those "*desired.sha1" files altogether (with a patch, for example), and change the rest so that it works without downloading those jars in any way? I have the feeling that the build process only downloads the jars that are described with a desired.sha1 In a perfect world, we'd use the version of those jars that are already packaged in Debian, and maybe put a symlink from their system-wide location to their location in the tree, so that the build process finds them. That would be really great. Adding those jars to the git (as it seems to be done for 2.9 -- Medhi, am I wrong?) seems ugly to me. I'd prefer to consider this as the last alternative only. It was unavoidable for versions older than 2.11 since scala depended on scala to bootstrap, but this has improved since then. Bye, Mt. -- Testis unus, testis nullius.
signature.asc
Description: Digital signature
