Hi!
> I failed to notice that you attached the port files to your first
> mail, I'm testing them right now. I'll get back to you
> in a few days.
After cleaning up the Makefile from the portlint-warnings,
it builds just fine on current@r348454M.
You can fine my version at
Hi!
> sorry to bother you again, but I was wondering why nobody noticed my
> message.
It's because we are all *very* busy 8-}, sorry for the delay.
As far as I understand, you prepared a new port, devel/renaissance,
and have problems during the build.
I failed to notice that you attached the
Hello all,
sorry to bother you again, but I was wondering why nobody noticed my
message.
Please do not take this in a negative way, but I would really appreciate
your feedback, one letter is enough:
A. The answer is obvious. If you cannot find it yourself, you should not be
doing this. Continue
On Thu, 13 Jun 2019, Andrea Venturoli wrote:
For years I've had my home on an NFSv3 server.
Finally I decided to move to NFSv4.
[...]
I got bitten quite badly by NFS in its early years; I see nothing much has
changed... I think it was to do with file-locking, I think.
-- Dave
On 13/06/2019 17:00, Steve Wills wrote:
Hmm, flavors have to be something that can be installed in parallel,
right? How does that impact binutils?
They don't /have/ to be something that can be installed in parallel.
Different flavours of the same package can conflict with each other.
Look at
Hi,
On 6/9/19 11:48 AM, Adam Weinberger wrote:
No, you're absolutely right. Flavours is the right way to do it now. I
keep forgetting about them, because I don't in any way understand how
to use them.
Hmm, flavors have to be something that can be installed in parallel,
right? How does that
On Thu, Jun 13, 2019 at 8:36 AM Andrea Venturoli wrote:
> Hello.
>
> For years I've had my home on an NFSv3 server.
> Finally I decided to move to NFSv4.
>
> Now the following happens every now and then (let's say, 1 out of 5
> times I launch it):
> _ FireFox is closed (no process running);
> _
Hello.
For years I've had my home on an NFSv3 server.
Finally I decided to move to NFSv4.
Now the following happens every now and then (let's say, 1 out of 5
times I launch it):
_ FireFox is closed (no process running);
_ I open FireFox and, while it works, a red message appears saying:
"The
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
