On Sunday 26 September 2010, Roland Smith wrote:
If you are upgrading to another major version of FreeBSD (say 7.x to
8.x), make a list of all used ports with `portmaster -l ports.list`.
Then delete all ports before updating the system. After the update,
re-install the 'root' and 'leaf' ports
I'm in doubt. I wanted to bring my ports collection uptodate, so I ran
csup -L 2 /root/ports-supfile and that updated my ports collection. At
least, I hope so.
Then I started googling and found that cvsup is not recommended. Better
tot use portsnap (???)
And also portupgrade was a no go. I
On Sun, Sep 26, 2010 at 06:29:17PM +0200, Dick Hoogendijk wrote:
Question: what is best used to have an up2date ports collection nowadays?
This system is FreeBSD8/amd64.
IMO if you don't mind compiling your own ports, use portsnap and
portmaster. The sequence is like this;
1) Run `portsnap
On 26/09/2010 17:29:17, Dick Hoogendijk wrote:
I'm in doubt. I wanted to bring my ports collection uptodate, so I ran
csup -L 2 /root/ports-supfile and that updated my ports collection. At
least, I hope so.
Then I started googling and found that cvsup is not recommended. Better
tot use
On 26-9-2010 19:13, Matthew Seaman wrote:
Really either of those two will serve you well, as will various others
I like portupgrade.
One question about dependencies: if I want to update *one* port I have
to run portupgrade -R portname, right.
But *when* do I run portupgrade -R ,name c.q.
On 26/09/2010 18:50:32, Dick Hoogendijk wrote:
On 26-9-2010 19:13, Matthew Seaman wrote:
Really either of those two will serve you well, as will various others
I like portupgrade.
One question about dependencies: if I want to update *one* port I have
to run portupgrade -R portname, right.
On Sun, 26 Sep 2010, Dick Hoogendijk wrote:
I'm in doubt. I wanted to bring my ports collection uptodate, so I ran csup
-L 2 /root/ports-supfile and that updated my ports collection. At least, I
hope so.
Then I started googling and found that cvsup is not recommended. Better tot
use
Woh, I'm confused now.
Question: what is best used to have an up2date ports collection nowadays?
portsnap fetch extract update for the first time after you've setup
the FreeBSD for the very first time. As the parameters used, it fetch
the ports tree, extract it to /usr/ports and update it.
On Friday 24 September 2004 03:55 pm, W. D. [EMAIL PROTECTED] wrote:
snip
OK, how about adding a cron job by root like this?
(Line will wrap. Everything between '===' on one line)
==
15 3 * * * /usr/local/bin/cvsup -h
W. D. wrote:
At 23:11 9/24/2004, Donald J. O'Neill wrote:
W.D. it's your cron job I'm looking, so I'll talk about it. It would
work, probably most of the time. Your example has both portsdb -Uu
and make index in it. Just use one, otherwise you're building INDEX-5
twice. Running pkgdb -fu (by
Oh, I must have had Donald's letter go into my bit bucket as I only saw
this message with his reply.
(Donald, you reply, Touché, as I was just joking.)
Anyhow, I did do it Donald's my way and I just like this other way
better for some reason. Sorry
Curtis
On 23 Sep, 2004, at 22:42, Günther
Oh, I must have had Donald's letter go into my bit bucket as I only saw
this message with his reply.
(Donald, you reply, Touché, as I was just joking.)
Anyhow, I did do it Donald's my way and I just like this other way
better for some reason. Sorry
Curtis
On 23 Sep, 2004, at 22:42, Günther
On Friday 24 September 2004 04:35 pm, Curtis Vaughan wrote:
Oh, I must have had Donald's letter go into my bit bucket as I
only saw this message with his reply.
(Donald, you reply, Touché, as I was just joking.)
Anyhow, I did do it Donald's my way and I just like this other
way better for
At 14:44 9/23/2004, Chris, wrote:
You could join in the FreeBSD tradition, though, and do it the
Right Way(tm) ...
http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html
An excellent tutorial/article by Dru Lavigne
Kevin Kinsey
OK, after reading this tutorial, here is MY new
W. D. wrote:
At 14:44 9/23/2004, Chris, wrote:
You could join in the FreeBSD tradition, though, and do it the
Right Way(tm) ...
http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html
An excellent tutorial/article by Dru Lavigne
Kevin Kinsey
OK, after reading this tutorial, here is MY
On Friday 24 September 2004 06:32 pm, Chris wrote:
W. D. wrote:
At 14:44 9/23/2004, Chris, wrote:
You could join in the FreeBSD tradition, though, and do it
the Right Way(tm) ...
http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.htm
l
An excellent tutorial/article by Dru
At 23:11 9/24/2004, Donald J. O'Neill wrote:
On Friday 24 September 2004 06:32 pm, Chris wrote:
W. D. wrote:
At 14:44 9/23/2004, Chris, wrote:
You could join in the FreeBSD tradition, though, and do it
the Right Way(tm) ...
http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.htm
l
There might be something to be said for doing it my way,
after all, Frank Sinatra made a fortune in that manner...
/tongue'n'cheek
You could join in the FreeBSD tradition, though, and do it the
Right Way(tm) ...
http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html
An excellent
Curtis Vaughan wrote:
There might be something to be said for doing it my way,
after all, Frank Sinatra made a fortune in that manner...
/tongue'n'cheek
You could join in the FreeBSD tradition, though, and do it the
Right Way(tm) ...
http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html
On Thursday 23 September 2004 02:44 pm, Chris wrote:
Curtis Vaughan wrote:
There might be something to be said for doing it my way,
after all, Frank Sinatra made a fortune in that manner...
/tongue'n'cheek
You could join in the FreeBSD tradition, though, and do it the
Right Way(tm)
Donald J. O'Neill wrote:
On Thursday 23 September 2004 02:44 pm, Chris wrote:
Curtis Vaughan wrote:
There might be something to be said for doing it my way,
after all, Frank Sinatra made a fortune in that manner...
/tongue'n'cheek
You could join in the FreeBSD tradition, though, and do it the
Hi all,
It seems like the message below doesn't belong on this list unless
I completely misunderstood the purpose of it.
If I'm wrong please let me know.
Cheers
snipped
Taking into consideration other issues or options pointed out
on the web tutorial, will this be a good strategy from now on
for
I got a lot of feedback earlier about ways to do port upgrades and I
really appreciate it.
I know everyone has their own way. For now, I am doing it the following
way. I just want to know whether there is any reason I shouldn't be
doing it this way. In other words, by doing it this way is
On Tuesday 21 September 2004 12:40, Curtis Vaughan wrote:
Then I run:
portupgrade -a
That's it.
You missed the most important middle step:
less /usr/ports/UPDATING
to see what critical changes have been made in the meantime that will affect
your system. For example, the www/apache2
OK, I took Donald on with his test and this is what I got:
Here's my INDEX-5 info before running portversion
4947853 Mar 15 2004 INDEX-5
and here it is after
5804696 Sep 21 13:54 INDEX-5
So, a definite change.
And when I ran portversion -vL= the first time, I got the info provided
immediately
Curtis Vaughan wrote:
OK, I took Donald on with his test and this is what I got:
Here's my INDEX-5 info before running portversion
4947853 Mar 15 2004 INDEX-5
and here it is after
5804696 Sep 21 13:54 INDEX-5
So, a definite change.
There might be something to be said for doing it my way,
after
26 matches
Mail list logo
