Hi,
Shane Ambler said :
> > My question therefore is: while I will mention these problems
> > upstream, should I also make the PR? Contact the port maintainer
> > directly? I understand it is not FreeBSD specific (same issue on
> > Debian Sid) however it really make the current port unusable for
>
On Fri, Jun 21, 2013, at 2:42, Aymeric Mansoux wrote:
>
> My question therefore is: while I will mention these problems upstream,
> should I also make the PR? Contact the port maintainer directly?
> I understand it is not FreeBSD specific (same issue on Debian Sid)
> however it really make the cu
On 21/06/2013 17:12, Aymeric Mansoux wrote:
My question therefore is: while I will mention these problems
upstream, should I also make the PR? Contact the port maintainer
directly? I understand it is not FreeBSD specific (same issue on
Debian Sid) however it really make the current port unusable
Hello everyone,
I am a FreeBSD newbie. I started to use it regularly for the first time
a couple of weeks ago and at the moment I am happily running
10.0-CURRENT with a custom kernel on my Thinkpad x61.
One of the software that I also started to use a couple of weeks ago
(acme from the plan9port
