Date: Thu, 17 Jan 2019 14:42:04 -0800 From: Enji Cooper <yaneurabeya@gmail.com> To: Maxim Sobolev <sobomax@freebsd.org> Cc: Cy Schubert <Cy.Schubert@cschubert.com>, "Conrad E. Meyer" <cem@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r343118 - in head/usr.sbin: . trim Message-ID: <EB1F82C3-B704-42C7-B6EA-ED7E49559FFC@gmail.com> In-Reply-To: <CAH7qZftZnugWaerpBdjCDapYfwmbm85r4fXQkR0eze02DkcyuQ@mail.gmail.com> References: <cem@freebsd.org> <CAG6CVpX78rHMtWTm97We50qy_D2jX79upn-9TjMy90cZeyVecQ@mail.gmail.com> <201901172046.x0HKkvWs011502@slippy.cwsent.com> <CAH7qZftZnugWaerpBdjCDapYfwmbm85r4fXQkR0eze02DkcyuQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] > On Jan 17, 2019, at 2:25 PM, Maxim Sobolev <sobomax@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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEtvtxN6kOllEF3nmX5JFNMZeDGN4FAlxBBLwACgkQ5JFNMZeD GN5Oog//eg4gG5Onqnn9+CKOMxhk+ELELTyd4gb2Yx81EmpBdHpusExAI8eZfhzQ e5Grt7jipkNeqPUaLlEmRGBbYSHbq7mE2tHQ8SIkLdWHt72YZ2Rco43TbXlmzzIF ka+A1A+6jkBPk1qez1RHYoMs2F3jdND+1SvGnwAqWeMklMD9RAfy0QCFe3uh87cZ sApG8b8zzn7hk3VTGn1pJJzKZGZUOCYxBrZcO6zckEdiqoLmMPsCcRHG3/xJ7jRW MyiblPqeKdNMEXPzKmO/RRb5Dbjq2hXbrKWI0HCb8EwKt8KUCOWSIy+C7OLBxlQS ArpJA+xo8zVvMitb+kekxupjfYBZlPBDOV2aSQLCXAZj4jQI9hqRQOqYBw0Kt72q FH5HjteRrcIdaamrHt6lRvYPBe4SBWvd7jomFhxCiWSg+jvx0rC9zFC+4uSzqEsr v16ZLSmnPP0e5OltgGP0JM7fNkMxhU2o9VVglaR3OhhuouvXml4iXGncsdoIeeEn E9qNm6xW5GnPdu81CRgtpOAQ6JHbJ2/rYcgPt7SAiVh3Qm2RNFyLbGcWXYTo5Pgv sCEwhR2ENCgwpqpFSHkKB0wpWE3ZskTjMFhvirDYm91R/6NRuEPc5k8gpMEOOKii E8Mbb2Y/pTd4iK8O01wL4dPkFfLkWZsNBP6n5ootb1hI7iKmKjE= =RYxu -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EB1F82C3-B704-42C7-B6EA-ED7E49559FFC>