On Sat, May 14, 2016 at 11:25:08AM +0800, Julian Elischer wrote:
> so who or what decides if I can put this in?
portmgr. From the portmgr pages:
Changes to bsd.port.mk are not the only commits that can have a drastic
effect on the tree. We request that any such changes also be tested on
th
On 13/05/2016 12:11 AM, Julian Elischer wrote:
so who or what decides if I can put this in? As a long term committer
from before there were ports, do I have access to it?
do I need to get a ports mentor? (seems likely and would make sense)..
do I apply somewhere? Or should I look for soemone i
Hi!
> wxGlade hasn't been updated since 20141026, when wxGlade-0.7.0 was
> released. The latest version is 0.7.2 .
Thanks to Walter Schwarzenfeld, this has been updated and the
problem with running it from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202688
was tested and fixed as well. Th
The makepatch target makes the patches in FILESDIR.
should it not make them in PATCHDIR?
they are defined by default to be the same thing:
PATCHDIR?= ${MASTERDIR}/files
FILESDIR?= ${MASTERDIR}/files
but it would seem to make more sense to have them appear in PATCHDIR
On 13 May 2016 at 04:08, Ed Maste wrote:
> Baptiste and I have been looking at reproducible builds in the FreeBSD
> ports tree, and one thing we'll need is a consistent timestamp that
> doesn't change when a port is rebuilt without changes.
>
> We considered a few different ideas, and have settle
On Fri, May 13, 2016 at 01:58:51PM +0200, Ben Woods wrote:
> On Thursday, 12 May 2016, Ed Maste wrote:
>
> > Baptiste and I have been looking at reproducible builds in the FreeBSD
> > ports tree, and one thing we'll need is a consistent timestamp that
> > doesn't change when a port is rebuilt wit
On Thursday, 12 May 2016, Ed Maste wrote:
> Baptiste and I have been looking at reproducible builds in the FreeBSD
> ports tree, and one thing we'll need is a consistent timestamp that
> doesn't change when a port is rebuilt without changes.
>
> We considered a few different ideas, and have settl
On 13/05/2016 3:26 PM, Andrzej Tobola wrote:
On Fri, May 13, 2016 at 12:11:47AM +0800, Julian Elischer wrote:
This patch is pretty self explanatory.
it allows us to keep patches for various ports separately in a sparse
hierarchy while not having to write to the ports tree itself.
In case the l
On Fri, May 13, 2016 at 12:11:47AM +0800, Julian Elischer wrote:
> This patch is pretty self explanatory.
>
> it allows us to keep patches for various ports separately in a sparse
> hierarchy while not having to write to the ports tree itself.
>
> In case the list scrubs hte text attachment (dif
On 13/05/2016 3:19 AM, Julian H. Stacey wrote:
Julian Elischer wrote:
This patch is pretty self explanatory.
it allows us to keep patches for various ports separately in a sparse
hierarchy while not having to write to the ports tree itself.
Nice idea ! I'll have a look.
BTW I've had something
10 matches
Mail list logo
