On Mon, 22 Jul 2019 11:00:42 +0200 Jaco Kroon <j...@uls.co.za> wrote:
> USE flag to enable/disable bundled packages. Any packages that gets
> committed with this USE flag goes off to a build server that builds the
> package and prepares an install (without bundled) and then the man pages
> can be scraped from the prepared install I reckon and placed on a
> standard URL, say d.g.o/manpages/${CATEGORY}/${PVR}.tar.gz ... possibly
> an eclass may be required I don't know, haven't thought about it that much.
In general, I really do like these suggestions for a dedicated USE flag
for use on gentoo automated build servers.
I think in general, this idea could even be extended to achieve more
than just pure MAN page generation, just implementation could be a bit
spicy, maybe even need future EAPI changes.
If the end result is a collection of asset tarballs of some kind that
contain various aspects of the same package, where the ebuild itself
dictates how the ebuild should be built on the build server, then it
enables us to approximate debian-esque deployment models where
"maintainer decides what aspects you get", but without the need to
strip end-users of essential utility.
Though I suspect *literally* using USE flags for this as-is might be
the wrong approach, as that just causes user-side pollution :/
Perhaps there's an Out-Of-Band strategy that can be employed, maybe
even using files not currently under PMS control.
IDK. I do get the impression we're "on the right track" with this, just
I don't like the proposals as-stated completely.
pgpQ2oFSI1YFs.pgp
Description: OpenPGP digital signature
