svn commit: r412019 - head/games/tbe
John Marino (FreeBSD)
freebsd.contact at marino.st
Tue Mar 29 08:09:42 UTC 2016
On 2016-03-29 10:00, Alexey Dokuchaev wrote:
>> 2) Repocopy makes sense to me ONCE, when creating a new port. After
>> the
>> port is created, don't use it within a port. I don't see people doing
>> this and I'm glad about that. If we said it's okay returning
>> pkg-plist,
>> then you can claim it's okay for returning patch files, which is
>> absurd.
>
> That seems arguable; I would consider repocopying even patches if
> changes
> warrant it, and would certainly repocopy any pkg-* files. It really
> helps
> to keep the dots connected and makes archaeology much easier. Once you
> get into the habit of studying the history before making any changes on
> a
> port this becomes quite conspicuous.
Recopy is not free. There is a price of effort to do this. It slows
maintenance down. If somebody is truly doing geneology on a particular
port, svn holds enough information. Suggesting to repocopy individual
files in a port is too much for benefit of 0.00001% of the time somebody
will find such effort useful.
Let's not put up even more barriers to maintenance. "Keeping dots
connected" doesn't demonstrate a real benefit to me. Surely svn has
some kind of "diff between revs" feature that could be used by anyone
that cares (which I assume is truly nobody once the academic arguments
are put aside).
John
More information about the svn-ports-all
mailing list