monorepo wtf
Thorsten Glaser
t.glaser at tarent.de
Mon Jan 31 20:24:37 UTC 2022
On Mon, 31 Jan 2022, Sergey Nazarkin wrote:
> file structure remains the same, the only difference is a number of
> mercurial commands required to fetch entire repo.
This is assuming we were using those. We weren’t.
We were downloading the tarballs corresponding to the tags
from each individual repository AND the hotspots for aarch32
AND aarch64-shenandoah, as well as a couple other things such
as icedtea-sound, *individually*, processing these for legal
reasons (unfree json.org code from Crackford, removal of some
embedded courtesy code copies), packing them up and creating
the source archive from this multi-tarball setup.
At build time, the right ones are chosen (again, this includes
special handling for aarch{32,64-shenandoah}), unpacked and
patched suitably.
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen:
╳ HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!
****************************************************
More information about the aarch32-port-dev
mailing list