Hi ports --
Here's a minor update to Tetzle. Mostly additional translations.
OK?
~Brian
Index: Makefile
===
RCS file: /cvs/ports/games/gottcode/tetzle/Makefile,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 Makefile
--- Makefile
Hola!
This trivial update brings node to the latest version.
Tested on amd64 with all node-* ports.
OK?
Index: Makefile
===
RCS file: /cvs/ports/lang/node/Makefile,v
retrieving revision 1.23
diff -u -p -r1.23 Makefile
--- Makefile
Hi (again),
here's a diff for nsh, openmdns, libgtop2 and wide-dhcp. I hope I got
the _KERNEL dance right... The only remaining offender seems to be
Zabbix.
Bonus strlcpy "fix" for openmdns.
OK? Comments?
Index: devel/libgtop2/Makefile
Hi ports --
Here's a diff to update audio/musique. An i386 tester would be much
appreciated. Also, the information icon seems to have disappeared when
running outside a DM (fluxbox, in my case) - you'll notice some blank
space after the "Skip to the next track" button - so a cluebat for that
On 2013/11/25 17:04, Matthieu Herrb wrote:
> Hi,
>
> Sorry I don't have time to prepare a patch now, just whining here...
Yes the following are known fallout from splitting if.h, no need to
report them ;)
devel/libgtop2
net/miniupnp/miniupnpd
net/openmdns
net/wide-dhcp
net/wmnetload
net/zabbix
Hi,
Sorry I don't have time to prepare a patch now, just whining here...
cc -c -o ../src/drivers/driver_openbsd.o -O2 -pipe -I../src -I../src/utils
-I/usr/local/include/PCSC -DCONFIG_BACKEND_FILE -DCONFIG_PEERKEY
-DCONFIG_DRIVER_WIRED -DCONFIG_DRIVER_OPENBSD -DEAP_TLS -DEAP_PEAP -DEAP_TTLS
On Mon, Nov 25, 2013 at 03:57:53PM +0100, Marc Espie wrote:
> On Mon, Nov 25, 2013 at 12:14:04AM +0100, Juan Francisco Cantero Hurtado
> wrote:
> > The problem with some .xz files was the limited datasize of VAX (40MB).
> > miod@ increased the limits to 128MB with his last commits.
> >
> > OK?
>
On Mon, Nov 25, 2013 at 12:14:04AM +0100, Juan Francisco Cantero Hurtado wrote:
> The problem with some .xz files was the limited datasize of VAX (40MB).
> miod@ increased the limits to 128MB with his last commits.
>
> OK?
Okay for the patch.
Your explanation of the problem is wrong, though. vax
Makes less sense today than it did a few years ago.
Okay to kill it completely.
That should be bsd.port.mk, Makefile.template, bsd.port.mk(5), sqlports
and individual ports, if memory serves.
Possibly also www but I haven't checked.
On Mon, Nov 25, 2013 at 2:41 AM, Stuart Henderson wrote:
> On 2013/11/24 17:01, Amit Kulkarni wrote:
> > can somebody please add it in the desired place?
>
> Is VMEM_WARNING actually useful for anything? I'd rather just remove it.
> It is currently added ad hoc to ports where the maintainer think
On Sun, Nov 24, 2013 at 09:00:24PM -0600, Shawn K. Quinn wrote:
> On Sun, Nov 24, 2013, at 07:33 AM, Pascal Stumpf wrote:
> > Whoops, forgot one diff to go along with this; add *.tar.bz to
> > EXTRACT_CASES:
>
> Are you sure this is .tar.bz and not .tar.bz2?
>
Yes. Search the tarballs in the pro
25.11.2013 15:14 пользователь "David Coppa" написал:
>
> On Mon, Nov 25, 2013 at 12:11 PM, Stuart Henderson
wrote:
> > On 2013/11/25 10:02, Antoine Jacoutot wrote:
> >> On Mon, Nov 25, 2013 at 08:41:53AM +, Stuart Henderson wrote:
> >> > On 2013/11/24 17:01, Amit Kulkarni wrote:
> >> > > can
On Mon, Nov 25, 2013 at 12:11 PM, Stuart Henderson wrote:
> On 2013/11/25 10:02, Antoine Jacoutot wrote:
>> On Mon, Nov 25, 2013 at 08:41:53AM +, Stuart Henderson wrote:
>> > On 2013/11/24 17:01, Amit Kulkarni wrote:
>> > > can somebody please add it in the desired place?
>> >
>> > Is VMEM_WAR
On 2013/11/25 10:02, Antoine Jacoutot wrote:
> On Mon, Nov 25, 2013 at 08:41:53AM +, Stuart Henderson wrote:
> > On 2013/11/24 17:01, Amit Kulkarni wrote:
> > > can somebody please add it in the desired place?
> >
> > Is VMEM_WARNING actually useful for anything? I'd rather just remove it.
> >
On Mon, Nov 25, 2013 at 08:41:53AM +, Stuart Henderson wrote:
> On 2013/11/24 17:01, Amit Kulkarni wrote:
> > can somebody please add it in the desired place?
>
> Is VMEM_WARNING actually useful for anything? I'd rather just remove it.
> It is currently added ad hoc to ports where the maintain
On 2013/11/24 17:01, Amit Kulkarni wrote:
> can somebody please add it in the desired place?
Is VMEM_WARNING actually useful for anything? I'd rather just remove it.
It is currently added ad hoc to ports where the maintainer thinks it uses
"a lot of memory" but that isn't really useful without ref
16 matches
Mail list logo