jmq/Documentation
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

pkgmeek.8: revised the concluding paragraph under Program Design

Browse Source
This commit is contained in:
John McQuah 2022-06-13 16:59:30 -04:00
parent 5a0d76543f
commit de5bbb0198
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
man8/pkgmeek.8
View File

@ -177,10 +177,14 @@ place where new code should be added.
Time will only tell whether this design can be retained as core maintainers come and go. At the time
of writing, patch submissions on our bug tracker are nowhere near the volume they were in 2017.
Either the interest in CRUX is waning (and could stand to be reinvigorated), or the would-be
contributors start paging through a legacy code base and lose confidence in their ability to help
out. Whichever the explanation, \fBpkgmeek\fP is offered as a partial remedy to the problem that
"we don't have people that actually sign up to care about our core tools" (FS#1410).
The patch submissions that do arrive are not dealt with in a timely manner, which is more easily
explained by a reduction in the number of core developers than by stipulating that CRUX package
tools have reached full maturity and cannot gain much benefit from new patches. The next most
probable explanations for the slow response to bug reports are: 1, interest in CRUX is waning (and
could stand to be reinvigorated), or 2, the would-be contributors start paging through a legacy code
base and lose confidence in their ability to help out. If either of these latter explanations has
any merit, \fBpkgmeek\fP is offered as a partial remedy to the problem that "we don't have people
that actually sign up to care about our core tools" (FS#1410).
.SH SEE ALSO
pkgmk.conf(5), Pkgfile(5), pkgadd(8), pkgrm(8), pkginfo(8), rejmerge(8), signify(1), curl(1), wget(1)