https://bugs.freedesktop.org/show_bug.cgi?id=56131
Matúš Kukan <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Matúš Kukan <[email protected]> --- (In reply to comment #3) > My view is that it might work the following way: > > + configuire.ac will has something like: > > BLABLA_TARBALL= > if <we want a 3rd party tarball because of a feature> ; then > BLABLA_TARBALL="blabla-<version>.tar.gz" > fi > AC_SUBST(BLABLA_TARBALL) > > > + ooo.lst.in would include: > @BLABLA_TARBALL@ So, this is current state, but there is demand for --with-all-tarballs See also https://gerrit.libreoffice.org/#/c/1088/ It would be more complicated. To be more flexible, I've moved some parts of download to configure and Makefile.fetch. And also ooo.lst ~> download.lst where the names are defined. The result is in feature/download branch. I am not sure what others will think about it, let's see. Quite possibly it's not perfect. > + download would read ooo.lst and download only the defined tarballs > get $BLABLA_TARBALL from a given URL (see below my idea about the URL) > get $BLABLA_TARBALL.md5 from the same URL > check md5 to make sure that the tarball is valid > If anyone thinks it's going to be better this way, I am willing to hack also on this but I think first we need $BLABLA_TARBALL.md5 files uploaded in http://dev-www.libreoffice.org/src/ > This way, we could use the original tarballs and need to define tarball > names only once in configure.ac as suggested by David. yep, modulo the names are in download.lst in feature/download -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
