> portmanager -u -f -l -y
>
> will rebuild all of the installed ports in a logical manner as well as
> creating a log file for the user to examine if necessary.
I will try that, thx!
I will also look in to:
portmanager
portsclean
portsnap
portversion
(any others?)
__
On 2/5/06, Robert Huff <[EMAIL PROTECTED]> wrote:
>
>
> Xn Nooby writes:
>
> > Everyone that knows what they are doing never seem to have a problem.
>
> Respectfully, rubbish.
> I use portupgrade; where it seems applicable I am careful to
> mention one ought to read the manual comp
Xn Nooby writes:
> Everyone that knows what they are doing never seem to have a problem.
Respectfully, rubbish.
I use portupgrade; where it seems applicable I am careful to
mention one ought to read the manual completely, and to state my
experiences where it has clearly and with
Xn Nooby wrote:
> > I want to ask you: how long does it take you to cvsup your ports, run
> > 'portsdb
> > -Uu', and finish with 'portversion -l "<" '? To run 'portsnap fetch
> > update',
> > then 'portversion -v | grep needs', it took less then 55 seconds and I was
> > off upgrading ports. The pr
> I want to ask you: how long does it take you to cvsup your ports, run
> 'portsdb
> -Uu', and finish with 'portversion -l "<" '? To run 'portsnap fetch
> update',
> then 'portversion -v | grep needs', it took less then 55 seconds and I was
> off upgrading ports. The procedure I used had no errors.
On Saturday 04 February 2006 16:56, Xn Nooby wrote:
> By the looks of it when you cvsup you get everything (src-all,
>
> > ports-all, etc) all at once. I think it might be better if you split
> > that into two sup-files where you would have one for the system,
> > src-all, and the other one for por
By the looks of it when you cvsup you get everything (src-all,
> ports-all, etc) all at once. I think it might be better if you split
> that into two sup-files where you would have one for the system,
> src-all, and the other one for ports. This way you don't have to
> rebuild the system every time
On 04 Feb 2006 16:12:29 -0500, Lowell Gilbert
<[EMAIL PROTECTED]> wrote:
> Nikolas Britton <[EMAIL PROTECTED]> writes:
>
> > No, If I remember right (someone step in if I'm wrong) make fetchindex
> > is what you would get if you ran portsdb -Uu.
>
> Assuming nothing has been checked in between (1)
Nikolas Britton <[EMAIL PROTECTED]> writes:
> No, If I remember right (someone step in if I'm wrong) make fetchindex
> is what you would get if you ran portsdb -Uu.
Assuming nothing has been checked in between (1) the building of the
index on the server (which you get from fetchindex), and (2) th
Nikolas Britton writes:
> 4. pkg_version | grep "<"
Consider instead:
portsversion -l "<"
to which I usually append:
| sendmail huff
in case I want to do the upgrade later.
Robert Huff
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today Xn Nooby spake forth boldly:
It just does, after you cvsup new ports cd into /usr/ports and type
make fetchindex. what way is the "old foolproof way"?
Here is how I update my system (without using a 'make fetchindex')
cvsup -g -L 2 /roo
Denny White wrote:
Today Xn Nooby spake forth boldly:
It just does, after you cvsup new ports cd into /usr/ports and type
make fetchindex. what way is the "old foolproof way"?
Here is how I update my system (without using a 'make fetchindex')
cvsup -g -L 2 /root/stable-supfile
less UPD
On 2/4/06, Xn Nooby <[EMAIL PROTECTED]> wrote:
>
>
> > It just does, after you cvsup new ports cd into /usr/ports and type
> > make fetchindex. what way is the "old foolproof way"?
> >
>
> Here is how I update my system (without using a 'make fetchindex')
>
> cvsup -g -L 2 /root/stable-supfile
>
> It just does, after you cvsup new ports cd into /usr/ports and type
> make fetchindex. what way is the "old foolproof way"?
>
Here is how I update my system (without using a 'make fetchindex')
cvsup -g -L 2 /root/stable-supfile
less UPDATING
make buildworld
make buildkernel
make insta
On 2/1/06, Xn Nooby <[EMAIL PROTECTED]> wrote:
> Since I've gone back to the "old foolproof way" of updating my system, I'm
> doing a "portsdb -Uu" again - which has always taken forever to run on my
> various machines. Is there a way to speed it up (without replacing it), or
> has anyone looked a
Since I've gone back to the "old foolproof way" of updating my system, I'm
doing a "portsdb -Uu" again - which has always taken forever to run on my
various machines. Is there a way to speed it up (without replacing it), or
has anyone looked at it to see if it needs rewriting?
I worked at a place
16 matches
Mail list logo
