IRC channel logs

2025-03-16.log

back to list of logs

<fossy>stikonas: about your comment on xz PR, yes https sources are now permitted pre-openssl. mirrorless isn't really supported
<fossy>maybe we should force --mirrors
<fossy>especially because we use VCS snapshots for gnulib now, that requires a mirror
<fossy>sorry, we generate VCS snapshots*
<matrix_bridge><Andrius Štikonas> fossy: yeah, makes sense
<fossy>speaking of, we would really like mor mirrors, https://github.com/fosslinux/live-bootstrap/blob/master/DEVEL.md#running-a-mirror
<fossy>^ anyone :D
<Prizzom>I'm trying to get the Bootstrap javascript framework working. It this the support group?
<fossy>Lol
<daddy>Well, if you're down for about 1700 steps _before_ the webdev framework...
<aggi>anyway, since the question was raised few days ago: i do not intend to "avoid gcc/c++", gcc/c++ merely remain _optional_ for a complete system profile supported with an alternative toolchain
<aggi>this is an important difference
<aggi>because it was _not_ possible up until recently, to retain a complete system profile for development with any alternative toolchain (tinycc, cproc/qbe)
<aggi>another side note: it seems possible to keep the mentioned system profile synced against latest upstream, except for a dozen or two packages which were intentionally pinned to a specific version to avoid c++ dependencies
<aggi>almost all of the ~500 packages that i pulled into maintenance are synced against latest ~testing portage tree already
<aggi>fully supported by tinycc/alternative-toolchain/linux2-abi/musl-libc/static-linking
<aggi>and, it's a complete distribution that i was developing with for many years already, except for gcc47/linux5.10 optionally replaced with tinycc/linux2.4 since recently
<aggi>which means, it is possible to emit a complete distribution independent from gcc/clang/c++ latest kernel versions etc.
<aggi>and this does not(!) block any transition to g++/clang or any other architecture, because gcc can be bootstrapped with such a distribution
<aggi>it's just i am not interested in doing this myself, because a complete development system that i am rather happy with
<aggi>for example, the entire distribution compiles in ~3hours total with tinycc (it's fast, yes); i bought a cheapo $30 thin client for this on ebay (t620 with a low-power quadcore)
<aggi>and it isn't neither necessary nor desireable to develop with c++/g++/clang on such
<aggi>yet you couldn't have a fully source-based free-software workflow on low-power systems up until recently, you were _forced_ to transition to g++/clang, because there wasn't alternative toolchain support available with tinycc for a complete posix development system
<aggi>my system profile avoids this problem, because gcc/c++ are optional
<aggi>and, with regards to bootstrapping, a _complete_ posix development host can be provided far earlier, long before g++/clang dependency graph build up
<matrix_bridge><Andrius Štikonas> ekaitz: https://github.com/oriansj/M2-Planet/releases/tag/Release_1.12.1
<matrix_bridge><Andrius Štikonas> I probably won't do another stage0-posix release today, maybe next weekend
<matrix_bridge><Andrius Štikonas> or do you need that one too?
<ekaitz>no, m2planet is enough
<ekaitz>thank you!