Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Mar 2009 16:05:47 -0500
From:      Charles Howse <chowse@charter.net>
To:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: portsnap ignores REFUSE directives
Message-ID:  <E87ABC10-65C0-41B7-9300-E14D4EA27BA4@charter.net>
In-Reply-To: <A09EA534-5F0D-4170-ABD4-DCACE0DBE3FB@charter.net>
References:  <6377DBBF-8969-471B-B06E-AC744D1E6CB9@charter.net> <20090316192810.3c2fef44@gumby.homeunix.com> <A09EA534-5F0D-4170-ABD4-DCACE0DBE3FB@charter.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

On Mar 16, 2009, at 2:43 PM, Charles Howse wrote:

>
> On Mar 16, 2009, at 2:28 PM, RW wrote:
>
>> On Mon, 16 Mar 2009 12:18:06 -0500
>> Charles Howse <chowse@charter.net> wrote:
>>
>>> Hi,
>>> I just installed 6.4-RELEASE on the way to -STABLE.
>>> I chose NOT to install the ports during installation.
>>> I configured /etc/portsnap.conf, uncommenting the REFUSE directives,
>>> because I only speak English.
>>>
>>> I created the proper directories, including /usr/ports.
>>> I ran 'portsnap fetch extract', and now I find arabic, chinese,
>>> french, german, hebrew, hungarian, etc. in my ports tree.
>>>
>>> What might be the problem here?
>>
>> Are these directories actually populated with ports?
>>
>> If not, my guess is that it's simply ignoring ports that match the
>> category, rather than removing the category entirely.
>
> I checked the chinese, and yes, there are ports as well as the  
> makefile etc. under the port.
> Looks completely normal as if I wasn't using REFUSE.
>
> If you look at the /etc/portsnap.conf file, the lines look like this:
> #
> #
> # REFUSE this that t'other
> # REFUSE some more stuff
>
> I just deleted the '#' and left the space at the beginning of the  
> line.
> Surely that wouldn't fubar it, would it?
> I'll try again and remove the leading space, but I'n not optimistic.
>
> Is the portsnap author a member of this list?

I fired off a quick email to the portsnap author, and here is his reply:

>> Hello,
>> I was just wondering if you were answering questions about portsnap?
>> You might want to look at the thread on freebsd-questions titled  
>> 'portsnap ignores REFUSE directives'
>
> REFUSE directives must start a line in portsnap.conf -- your leading
> whitespace is making portsnap not recognize the option.

I guess that settles that.  :-)  Nice to know that folks higher in the  
FreeBSD 'food chain' are so quick to respond and help.




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?E87ABC10-65C0-41B7-9300-E14D4EA27BA4>