> 1) Are a lot of people using portupgrade? I've not had any problems with
> it, but it'd be nice to know that I'm not the only user on the planet.
> Any success stories? Failures?
I do a cvsup of my ports tree early every morning, immediately
followed by a portupgrade * of all entries in /var/db/pkg.
I haven't experienced difficulties, other than the occasional
bug in a port itself, usually resulting in a stop code displayed
for that particular port during the build. When that happens,
portupgrade just continues on with the next port in the list.
Of course, the duration of the process can vary greatly, depending
on how many (and which) ports were changed since the previous
cvsup. Most days, the whole thing is over in a minute, but there
are also those days when both XFree86 and KDE have upgrades in
the same morning -- and that can easily have things crunching
for more than an hour.
Quote:> 2) Some ports have a lot of compile-time options, ie mod_php4. When I
> upgrade it, I want to use the same options. Is there any way to handle
> this gracefully, short of making notes for future reference?
I haven't come up with an ideal solution to this yet. On some I can
handle things by setting environment variables, but for others such as
XFree86, I just hammer the responses in each time. I can see where it
would be nice to have it all automated in a hands-off batch style run,
but for my system it doesn't happen enough to be a real pain (yet!).
(remove 'revoke-my-' from address for email)