Re: portsnap update won't update original /usr/ports

2012-05-23 Thread RW 
On Tue, 22 May 2012 21:30:44 -0400 (EDT)
Thomas Mueller wrote:

 - Original Message -
 From: Gary Aitken free...@dreamchaser.org
 To: freebsd-questions@freebsd.org
 Sent: Tue, 22 May 2012 19:02:30 -0400 (EDT)
 Subject: portsnap update won't update original /usr/ports
 
 According to the handbook, one can do
portsnap fetch
portsnap update
 and the update will work with a previously created ports tree;
 I presume this includes one created during system install.

It says:

If you are running Portsnap for the first time, extract the snapshot
into /usr/ports: # portsnap extract

If you already have a populated /usr/ports and you are just updating,
run the following command instead...

If you have the tree from the disk then that means you are running
portsnap for the first time, the second sentence refers to a /usr/ports
populated by a portsnap extract.


  My response: 
 
 
 Now I wonder if it's feasible to switch between portsnap fetch
 update and csup ports-supfile, or if it's strictly one or the
 other.

You'll probably get away with it most of the time, but it's not safe to
mix them.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

portsnap update won't update original /usr/ports

2012-05-22 Thread Gary Aitken 

According to the handbook, one can do
  portsnap fetch
  portsnap update
and the update will work with a previously created ports tree;
I presume this includes one created during system install.

However, when I attempted this, portsnap complained:
  /usr/ports was not created by portsnap.
  You must run 'portsnap extract' before running 'portsnap update'.

Is there a way to use portsnap against this tree, or must I delete the 
existing /usr/ports and do an extract first?


Thanks,

Gary
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap update won't update original /usr/ports

2012-05-22 Thread Shane Ambler 

On 23/05/2012 08:32, Gary Aitken wrote:

According to the handbook, one can do portsnap fetch portsnap update
and the update will work with a previously created ports tree; I
presume this includes one created during system install.

However, when I attempted this, portsnap complained: /usr/ports was
not created by portsnap. You must run 'portsnap extract' before
running 'portsnap update'.

Is there a way to use portsnap against this tree, or must I delete
the existing /usr/ports and do an extract first?



'portsnap extract' will write over whatever is in /usr/ports so you
don't have to delete what is there. Any distfiles or packages will
remain intact.

You need to start with 'portsnap extract' so that portsnap gets a
reference point to use for updates - which only adds changes since last
update

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: portsnap update won't update original /usr/ports

2012-05-22 Thread Thomas Mueller 
- Original Message -
From: Gary Aitken free...@dreamchaser.org
To: freebsd-questions@freebsd.org
Sent: Tue, 22 May 2012 19:02:30 -0400 (EDT)
Subject: portsnap update won't update original /usr/ports

According to the handbook, one can do
   portsnap fetch
   portsnap update
and the update will work with a previously created ports tree;
I presume this includes one created during system install.

However, when I attempted this, portsnap complained:
   /usr/ports was not created by portsnap.
   You must run 'portsnap extract' before running 'portsnap update'.

Is there a way to use portsnap against this tree, or must I delete the 
existing /usr/ports and do an extract first?

Thanks,

Gary

 My response: 

I screwed up this way too, when I downloaded the USB memstick image for FreeBSD 
9.0_BETA1 and later, BETA2, I installed the ports from that, which worked to my 
disadvantage when I later ran portsnap fetch update.

I wound up deleting /usr/ports/* and starting fresh, may not necessarily have 
had to delete the ports tree.  But now it works.

Now I wonder if it's feasible to switch between portsnap fetch update and 
csup ports-supfile, or if it's strictly one or the other.

I am at webmail interface, which strongly favors top-posting over 
bottom-posting; feel more comfortable with vi editor.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org