Juan Miscaro wrote:
> --- Ingo Schwarze <[EMAIL PROTECTED]> wrote:
...
>> The standard way to handle upgrades is to update the src
>> on the master only, to build new release sets on the master,
>> and to use the official upgrade process to install these
>> new release sets on the clients. That way, none of the
>> clients will ever need source code.
>
>
> I'm embarrassed to say that I was intending to build my client systems
> locally.
Save yourself time and work, make a release.
> The ports tree can be useful though.
eh.
I keep telling myself that, but I hardly ever use it 'cept on a couple
machines. Those are usually NOT machines I'm installing packages to.
(i.e., I use the ports tree on my management console machines, but on
actual production machines, I never use it. I can look at the tree on
my machine I'm sitting at, rather than the machine I'm sshed into,
find what I need to know, then pkg_add -i whatever...)
>> > The trouble is that when I performed a test update of this code
>> > there was a immense amount of downloading taking place.
>> > This should not have been the case.
>>
>> Unless you tell us what you mean by "test update" (cvs update?
>> which server? which command, exactly?) even guessing is difficult.
unanswered important question.
>> In case you are talking about
>> cd /usr/src; cvs up -dP
>> this will take some time, even with a quick network link, using
>> a public mirror in your own country and without many changes.
>> For the above command, five minutes would seem normal even
>> using a 100 Mbit/s internet connection.
>
>
> But why should there be such a change if I just finished updating those
> same sources on the master?
Because you either did or expect something wrong. What, we don't know. :)
Even with a local CVS repository, a cvs update will take time, as it
compares a lot of data. IF you use the right/wrong options, it produces
a lot of output, which you may be misinterpreting as "changes", even
though it was just a progress report. ("-q" is your friend. usually).
If you really are getting large numbers of actual changes, you probably
aren't working with a -stable tree. If you didn't intend to, that's life,
lots of changes are made to the tree every day. If you did intend to,
your process is wrong, because you aren't. :)
Nick.
