Hi, Am Sonntag, den 06.05.2018, 10:28 +0200 schrieb Jonas Smedegaard: > Hi Robert, > > Excerpts from Robert Lemmen's message of maj 6, 2018 9:39 am: > > we are currently thinking about how to package perl 6 modules. One of > > the problems is that perl 6 pre-compiled modules and leaves these > > precomp files in hard-to-predict places. we could create these files > > during install-time on the target system, or at build time. If we do > > the latter, all modules would depend on a fairly tight version of the > > runtime, so we would need transitions to upgrade them all together. > > Details at https://wiki.debian.org/Perl6PreCompProposal is it just changes in the runtime that would require recompilations, or also changes in perl6 dependencies? > > I would love to get some input from you on how difficult "big" > > transitions are, and whether you think these could be made more often > > (e.g. up to once a month)? > > And if you have any tips on how to make > > these transitions less painful? The crucial ingredients to make this handleable, I think, are: * make sure that packages are uninstallable when they would not work (i.e. encode the dependencies in the binary’s Depends field, by depending on very specific versions and/or virtual packages that encode the ABI) * make sure you can rebuild the packages using binNMUs rather than source-full uploads (i.e. calculate the run-time dependencies at build time.) * create tools to schedule binNMUs, or use a theme that is compatible with what haskell and ocaml do, see: https://people.debian.org/~nomeata/binNMUs-haskell.txt * Kindly ask the wb-team people for access to wanna-build so that you can schedule binNMUs as needed. With these things in place, it is not too painful. Cheers, Joachim -- Joachim “nomeata” Breitner • nomeata@debian.org • https://j.oach.im/
Attachment:
signature.asc
Description: This is a digitally signed message part