Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Jan 2019 18:41:05 -0800
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        Enji Cooper <yaneurabeya@gmail.com>
Cc:        Maxim Sobolev <sobomax@freebsd.org>, 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:  <201901180241.x0I2f5wO057051@slippy.cwsent.com>
In-Reply-To: Message from Enji Cooper <yaneurabeya@gmail.com> of "Thu, 17 Jan 2019 14:42:04 -0800." <EB1F82C3-B704-42C7-B6EA-ED7E49559FFC@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <EB1F82C3-B704-42C7-B6EA-ED7E49559FFC@gmail.com>, Enji 
Cooper writes
:
> 
>
> --Apple-Mail=_6CB1620B-6707-4F06-B7FF-9F1ECBA36F56
> Content-Transfer-Encoding: quoted-printable
> Content-Type: text/plain;
> 	charset=utf-8
>
>
> > On Jan 17, 2019, at 2:25 PM, Maxim Sobolev <sobomax@freebsd.org> =
> wrote:
> >=20
> > 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=E2=80=99s 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=E2=80=99s 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).

Yes.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201901180241.x0I2f5wO057051>