svn commit: r515803 - head/devel/bazel

[Mathieu Arnold]

On Wed, Oct 30, 2019 at 11:15:00AM +0400, Gleb Popov wrote:
> On Wed, Oct 30, 2019 at 10:27 AM Mathieu Arnold <mat at freebsd.org> wrote:
> 
> > On Tue, Oct 29, 2019 at 09:33:10AM +0400, Gleb Popov wrote:
> > > My approach at least provide a stable binary package, and actually a
> > > way to build from source too - it just don't follow usual `make
> > > install` procedure.
> >
> > The problem with that is that comes from some false assumption.  It is
> > not *your* port.  As such it is not ok to have some obscure steps that
> > nobody else knows about.  Ports belong to everyone, and anyone should be
> > able to update a port.  If you have to do some arcane thing that is not
> > in the normal procedure to build a port, like pregenerating some binary
> > package (which is what the port is supposed to do in the first place),
> > then you are doing it wrong.
> >
> 
> Actually, there are many examples in our ports tree that use "arcane
> things".

Those are not examples, those are ports that fell through the cracks and
should be fixed.  Because, when a port needs some extra steps that only
the maintainer knows to do the update, then the port is bound to die the
day the maintainer's focus goes away.

The frameworks bits are documented and are not arcane, those that are
not should be.

> Again, I agree that making TensorFlow build the usual way is better than
> any other approach, but we can see that maintainer can't keep up with it.
> And no wonder - it is extermely large piece of software with unfriendly
> build system. So, I still lean toward prepackaged approach + documenting
> the procedure.

If the maintainer does not have the time to maintain the port and it
often gets broken, it will end up being marked BROKEN more often than
not, and will probably be removed.  I have absolutely no idea what
tensorflow is or does (and I probably never be interested in knowing),
though if it is as important as you make it seems, I am sure more than
one person can be found with enough interest to maintain it, and a team
can be formed to take on the maintainership.

-- 
Mathieu Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20191031/8a8a53a9/attachment.sig>