Re: portsnap temporary files

2017-01-06 Thread RW via freebsd-ports
On Sat, 7 Jan 2017 06:51:44 +1100 (EST) Dave Horsfall wrote: > Is there some reason why portsnap cannot clean > up /var/db/portsnap/files? I've just had to remove a zillion of them, > a bunch at a time because "rm" choked on the arg list. If you mean files under /var/db/portsnap/files/ then these

Re: portsnap temporary files

2017-01-06 Thread Dave Horsfall
On Fri, 6 Jan 2017, Xin LI wrote: > Because the files are still being used? What makes you believe they are > unused, by the way? How would I tell? Some were there since last October, surviving a few reboots... What I do see is the INDEX file containing "...|$tmpfile"; could that be the pro

Re: portsnap temporary files

2017-01-06 Thread Michelle Sullivan
Dave Horsfall wrote: (Many responses) I note that no-one has answered the question which caused me to post the message in the first place viz: why weren't the files being removed automatically? Everyone appears to have missed this point... I didn't and some of the answers are helpful even if n

Re: portsnap temporary files

2017-01-06 Thread Xin LI
Because the files are still being used? What makes you believe they are unused, by the way? On Fri, Jan 6, 2017 at 3:34 PM, Dave Horsfall wrote: > (Many responses) > > I note that no-one has answered the question which caused me to post the > message in the first place viz: why weren't the file

Re: portsnap temporary files

2017-01-06 Thread Bob Eager
On Sat, 7 Jan 2017 10:34:39 +1100 (EST) Dave Horsfall wrote: > (Many responses) > > I note that no-one has answered the question which caused me to post > the message in the first place viz: why weren't the files being > removed automatically? Everyone appears to have missed this point... > D

Re: portsnap temporary files

2017-01-06 Thread Dave Horsfall
(Many responses) I note that no-one has answered the question which caused me to post the message in the first place viz: why weren't the files being removed automatically? Everyone appears to have missed this point... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will s

Re: portsnap temporary files

2017-01-06 Thread Jonathan Chen
On 7 January 2017 at 11:30, Bob Eager wrote: > On Sat, 7 Jan 2017 06:51:44 +1100 (EST) > Dave Horsfall wrote: > >> Is there some reason why portsnap cannot clean >> up /var/db/portsnap/files? I've just had to remove a zillion of them, >> a bunch at a time because "rm" choked on the arg list. >> >

Re: portsnap temporary files

2017-01-06 Thread Bob Eager
On Sat, 7 Jan 2017 06:51:44 +1100 (EST) Dave Horsfall wrote: > Is there some reason why portsnap cannot clean > up /var/db/portsnap/files? I've just had to remove a zillion of them, > a bunch at a time because "rm" choked on the arg list. > > Perhaps a "portsnap clean" command? I'm surprised th

Re: portsnap temporary files

2017-01-06 Thread Dave Horsfall
On Fri, 6 Jan 2017, olli hauer wrote: > Why? For the reason I stated; I had to remove hundreds of them by hand. > As soon you run "portsnap fetch" old files in this directory are purged! Not here they weren't... > If you look into /var/db/portsnap/INDEX you can see the mapping of the > files

Re: portsnap temporary files

2017-01-06 Thread olli hauer
On 2017-01-06 20:51, Dave Horsfall wrote: > Is there some reason why portsnap cannot clean up /var/db/portsnap/files? > I've just had to remove a zillion of them, a bunch at a time because "rm" > choked on the arg list. > > Perhaps a "portsnap clean" command? I'm surprised that there isn't one

portsnap temporary files

2017-01-06 Thread Dave Horsfall
Is there some reason why portsnap cannot clean up /var/db/portsnap/files? I've just had to remove a zillion of them, a bunch at a time because "rm" choked on the arg list. Perhaps a "portsnap clean" command? I'm surprised that there isn't one. -- Dave Horsfall DTM (VK2KFU) "Those who don't

Re: using ports for things they were never meant to do

2017-01-06 Thread Lowell Gilbert
Julian Elischer writes: > So this seems to be a speciality of mine. > > I often find that I need a ports tree at rev X except for some port > foo/bar that needs to be at some different rev (Y) to pick up a > fix/change needed by the application. Now there is no reason that I > can't just edit t

Re: ports/devel/noweb/Makefile FETCH_* is wrong, comment out works.

2017-01-06 Thread Julian H. Stacey
> > Do feel free to open a PR about the regression :-) > > Thanks, Will do, Done. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215830 Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.

Re: using ports for things they were never meant to do

2017-01-06 Thread Michelle Sullivan
Julian Elischer wrote: So this seems to be a speciality of mine. I often find that I need a ports tree at rev X except for some port foo/bar that needs to be at some different rev (Y) to pick up a fix/change needed by the application. Now there is no reason that I can't just edit the distin

using ports for things they were never meant to do

2017-01-06 Thread Julian Elischer
So this seems to be a speciality of mine. I often find that I need a ports tree at rev X except for some port foo/bar that needs to be at some different rev (Y) to pick up a fix/change needed by the application. Now there is no reason that I can't just edit the distinfo file and the Makefile