Re: rsync'able ports tree instead of csup?

2008-05-13 Thread Matthew Seaman

Joachim Rosenfeld wrote:

On Tue, May 13, 2008 at 1:46 PM, Derek Buttineau <[EMAIL PROTECTED]> wrote:

Have you tried using portsnap?  It's a binary snapshot of the ports tree:
http://www.freebsd.org/doc/en/books/handbook/portsnap.html


Awesome, this is exactly what I was looking for.

I don't suppose there is something analagous to portsnap for the
source tree? It doesn't matter all that much because I don't update
/usr/src all that open, so running csup(1) when a new version comes
out is not a terribly big pain.


freebsd-update.  Comes with the system, is by the same person who wrote
portsnap.

However, it defaults to doing binary updates of the installed system. 
You need to tweak the config file if all you want are the system sources.


Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature


Re: rsync'able ports tree instead of csup?

2008-05-13 Thread RW
On Tue, 13 May 2008 13:27:05 -0400
"Joachim Rosenfeld" <[EMAIL PROTECTED]> wrote:

> My usual workflow with the ports tree (and to a lesser
> extent, /usr/src) goes something like this:
> 
> 1. download ports/src tree from cdrom/ftp site (usually done once)
> 
> 2. use csup to update to HEAD
> 
> 3. build

As I understand it, it's advisable  do an initial csup to the exact
version in the snapshot, before doing the csup to the latest
version. If you skip this then csup wont delete files removed
between the snapshot and the current tree. If you are unlucky that
could lead to persistent problems that are hard to diagnose.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: rsync'able ports tree instead of csup?

2008-05-13 Thread Joachim Rosenfeld
On Tue, May 13, 2008 at 1:46 PM, Derek Buttineau <[EMAIL PROTECTED]> wrote:
> Have you tried using portsnap?  It's a binary snapshot of the ports tree:
> http://www.freebsd.org/doc/en/books/handbook/portsnap.html

Awesome, this is exactly what I was looking for.

I don't suppose there is something analagous to portsnap for the
source tree? It doesn't matter all that much because I don't update
/usr/src all that open, so running csup(1) when a new version comes
out is not a terribly big pain.

thanks,
Joe
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: rsync'able ports tree instead of csup?

2008-05-13 Thread Kevin Downey
On Tue, May 13, 2008 at 10:27 AM, Joachim Rosenfeld
<[EMAIL PROTECTED]> wrote:
> My usual workflow with the ports tree (and to a lesser extent, /usr/src)
>  goes something like this:
>
> 1. download ports/src tree from cdrom/ftp site (usually done once)
>
> 2. use csup to update to HEAD
>
> 3. build
>
>  The problem is step 2. It takes a very long time for csup to apply the
>  latest changes from the cvsup servers to the tree, even if my previous
>  csup session was only the previous day.
>
>  IMO, something like rsync would be *way* faster for this task. I know
>  csup is CVS-tags aware and such, but 99% of the time, I'm just tracking
>  HEAD.
>
>  Would it be a good idea to setup a server that does nothing but
>  csup/cvsup ports, HEAD, and RELENG_7_0, and make that available via
>  rsync? It could be done frequently enough (maybe every 15 minutes) such
>  that most users would be fine with everything but the last 15 minutes.
>
>  Has anyone done something like this already?
>
>  thanks,
>  joe

man portsnap



-- 
The Mafia way is that we pursue larger goals under the guise of
personal relationships.
 Fisheye
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: rsync'able ports tree instead of csup?

2008-05-13 Thread Andreas Rudisch
On Tue, 13 May 2008 13:27:05 -0400
"Joachim Rosenfeld" <[EMAIL PROTECTED]> wrote:

> IMO, something like rsync would be *way* faster for this task.

Take a look at portsnap.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/portsnap.html

Andreas
--
GnuPG key  : 0x2A573565|http://www.gnupg.org/howtos/de/
Fingerprint: 925D 2089 0BF9 8DE5 9166  33BB F0FD CD37 2A57 3565


pgpBdIab9AdPe.pgp
Description: PGP signature


Re: rsync'able ports tree instead of csup?

2008-05-13 Thread Derek Buttineau

On 2008-May-13, at 1:27 PM, Joachim Rosenfeld wrote:

My usual workflow with the ports tree (and to a lesser extent, /usr/ 
src)

goes something like this:

   1. download ports/src tree from cdrom/ftp site (usually done once)

   2. use csup to update to HEAD

   3. build

The problem is step 2. It takes a very long time for csup to apply the
latest changes from the cvsup servers to the tree, even if my previous
csup session was only the previous day.



Have you tried using portsnap?  It's a binary snapshot of the ports  
tree:


http://www.freebsd.org/doc/en/books/handbook/portsnap.html

Derek

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"