On 18.02.2016 23:35, Alphons van Werven wrote:
Walter Schwarzenfeld wrote:
But this could be overwritten with the next update.
[snip]
But this could also [sic] overwritten.
You're using portsnap for your updates, I presume? Subversion will not
override local changes (at least not without
Walter Schwarzenfeld wrote:
> typos ... How should that work?
>
>
Very easily - but wouldn't necessarily solve your issue without a lot
more work...
as someone else pointed out you can use VALID_CATEGORIES+=local in your
/etc/make.conf file...
The '+' if you didn't realise is to append it on
Seems to work without "+", but looks like the right syntax with it. Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On Fri, 19 Feb 2016 09:18:11 +0100
Walter Schwarzenfeld wrote:
> Thanks -> echo 'VALID_CATEGORIES=local' >> /etc/make.conf is he
> simpelst way. Seems to work.
Don't you mean: VALID_CATEGORIES+=local ??
___
Thanks -> echo 'VALID_CATEGORIES=local' >> /etc/make.conf is he
simpelst way. Seems to work.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Hi,
the short answer: echo 'VALID_CATEGORIES=local' >> /etc/make.conf
On Thu, 18 Feb 2016, Walter Schwarzenfeld wrote:
If I make an own port, I had it add to the category/Makefile. But this
could be overwritten with the next update.
If I make an own category I had it add to
typos ... How should that work?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> You know you can all run your own portsnap server to allow you to
include local changes?
No, hoq ahouls rhat work?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Alphons van Werven wrote:
> Walter Schwarzenfeld wrote:
>
>
>> But this could be overwritten with the next update.
>>
> [snip]
>
>> But this could also [sic] overwritten.
>>
>
> You're using portsnap for your updates, I presume? Subversion will not
> override local changes (at
That's right, I use portsnap. I don't like svn.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On Thu, 18 Feb 2016 23:21:11 +0100
Walter Schwarzenfeld wrote:
> If I make an own port, I had it add to the category/Makefile. But this
> could be overwritten with the next update.
I make my own category - 'local'.
> If I make an own category I had it add to
Walter Schwarzenfeld wrote:
> But this could be overwritten with the next update.
[snip]
> But this could also [sic] overwritten.
You're using portsnap for your updates, I presume? Subversion will not
override local changes (at least not without asking first). I have a tree
here that contains
from portmaster||,||synth, etc.)
Is it considerable to make general a category customports or overlooked
I something?
It will be more simply, and good for the order in the ports tree. Better
as the own port are spread over the whole ports-tree.
(It only needs to make the category and add
13 matches
Mail list logo