hi,

i've been working over the last few days on getting dbscripts to
import i686 packages from archlinux32.org. this resulted on a single
script (db-import-pkg) shared by our 3 upstream providers, with common
routines from the previous separate scripts modularised, de-duplicated
and (briefly) documented. armv7h and i686 will also stop duplicating
arch=(any) packages first obtained from Arch proper.

that's it for the cursory announcement/overview of the impending
dbscripts release, which probably affects no one but our server.

on a related topic, we no longer have a (working) tool to retrieve
sources per package. Arch's [deprecation of ABS][] also spelled the end
of Parabola's dbscripts program that dealt with populating our own
ABS-like tree.

because .src tarballs are completely lacking from ALARM and Arch32,
it's clear to me that the only way forward is to pull from VC systems
themselves and cook one full Parabola source tree from there. that is,
one per upstream/architecture, overriding with customized PKGBUILDs.

but what about the client? what are your views regarding fixing and
continuing abs vs adopting and adapting the newer --and apparently
more complex-- [asp][]?

[deprecation of ABS]: https://www.archlinux.org/news/deprecation-of-abs/
[asp]: https://github.com/falconindy/asp

--
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Ring: c8ba5620e080bef9470efb314c257304ff9480f5
Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C
<https://isacdaavid.info/donate>

_______________________________________________
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev

Reply via email to