On 2025-06-01 14:23, Jon Turney via Cygwin-apps wrote:
On 04/05/2025 07:59, ASSI via Cygwin-apps wrote:
Takashi Yano via Cygwin-apps writes:
I pushed current working files in the packages
llvm
Thereby obliterating all the work I'd done two years ago in getting the
packaging halfway up to speed and making it a mess again. Not
impressed… :-(
Hmm... maybe this could be arranged better.
The idea of playground branches was all a bit ad-hoc after I initially had
things configured to only allow pushes to master (or main, I guess, now).
Perhaps it's possible to give every maintainer a branch only they can create,
push, force-push, rewind and delete?
Or maybe I just need to allow branches named 'topic/*' which is the convention
used elsewhere on sourceware for volatile, personal branches?
If it is in a repo, it can be rewound and replayed, or merged differently, so
nothing has been *obliterated*, although rework may be required to tidy it up!
Allowing any maintainer to use playground branches or the playground repo
provides enough flexibility for our purposes.
Reading thru the Sourceware security policy requirements, all maintainers,
including those not yet using cygport, like g-b-s or their personal hacks,
should check in *ALL* build scripts required and include them in their source
packages, to provide an externally reproducible source of packages.
I have been uncomfortable for a long time with packages which can be rebuilt or
updated only by their maintainers, who rarely seem to monitor the mailing lists.
If anything ever happens to their systems, they may be unable to rebuild or
update their packages, and there will be no possible alternatives, other than
starting from scratch.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
