> On Jan 17, 2019, at 2:25 PM, Maxim Sobolev <sobo...@freebsd.org> wrote: > > What I think we really need is some way to easily porti-ze useful stuff that > would otherwise go into /usr/[s]bin, so adding things would be just as easy > as hooking up SUBDIR into usr.[s]bin/Makefile. Yes, I know, this is topic > almost as old as the FreeBSD Project itself, but perhaps we just did not > approach it the right way. It was always the idea that we would just move > bunch of stuff from src/usr.[s]bin repo into ports/. Which brings several > important question such as "who is to host the distfile"? "where sources > hosted", "who is to update the port when changes happen?" etc.
Projects like this could be hosted on GitHub. Ports supports GitHub out of the box, so this seems like a low barrier for entry (the bonus of doing this is that the projects could potentially be used by other non-FreeBSD projects, and contributed by others outside the FreeBSD project; the downside is having to deal with FreeBSD CI, as Travis CI only supports Linux (IIRC making Travis support FreeBSD is a non-trivial project, but it’s likely a very worthwhile goal, as it would make it easier to catch issues upfront with third-party projects that FreeBSD consumes, like llvm), enforcing style (can be done with git commit hooks and GitHub checks), etc. I would really like to do these things because it’s difficult getting folks to support FreeBSD in third-party projects as-is. Lowering the barrier of entry would allow FreeBSD and its developers to better scale (and make FreeBSD more of a first-class OS). > Perhaps even by forking the whole ports idea into a smaller closely-guarged > subset. Something like a new baseports repository, which might have structure > like baseports/usr.bin/xxx, baseports/usr.sbin/yyy etc. Then add some > automagic glue to kick in on every commit and transfer this into valid ports, > which is going to be packaged by the poudriere and such. This way we could > reduce amount of port-foo average src committer needs in order to maintain > code. I am almost tempted to sit and write something over the next weekend or > few of thereofs. Using usr.sbin/trim as an example. Please see my above comment. Cheers! -Enji
signature.asc
Description: Message signed with OpenPGP
