Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Aug 2010 11:48:55 +0300
From:      Ion-Mihai Tetcu <itetcu@FreeBSD.org>
To:        Doug Barton <dougb@FreeBSD.org>
Cc:        freebsd-ports@freebsd.org, David Wolfskill <david@catwhisker.org>
Subject:   Re: Efficiency & correctness for port version upgrades
Message-ID:  <20100802114855.1b786820@it.buh.tecnik93.com>
In-Reply-To: <4C54B162.4000509@FreeBSD.org>
References:  <20100731120027.GN12818@albert.catwhisker.org> <4C54B162.4000509@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/ipQEiDv=1ZKKLt7gUt_ttk9
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sat, 31 Jul 2010 16:27:30 -0700
Doug Barton <dougb@FreeBSD.org> wrote:

> On 07/31/10 05:00, David Wolfskill wrote:
> > I have been using portmaster for updating the installed ports on
> > may machines -- thanks, Doug!
>=20
> My pleasure. :)
>=20
> > I'm in the habit of updating on a daily basis -- directly after the
> > "smoke-test" boot of a newly-rebuilt stable/7 (before I go on to
> > build stable/8).
> >=20
> > This morning, I noticed the (20100730) entry in UPDATING on
> > www/neon28 -> www/neon29, so I made sure to complete that before
> > doing the "svn update" on my stable/8 working directory.  [This is
> > one place where having the revision control system in ports, vs.
> > base, is a bit of a nuisance -- but that's off-topic for this note.]
> >=20
> > The instructions given for portmaster were:
> >=20
> >   Portmaster users:
> >         portmaster -o www/neon29 www/neon28
> >         portmaster -r neon29-
> >=20
> > which is fine, in that it works.
> >=20
> > However:  It also causes www/neon29 to be built twice; I cannot
> > help but question the extent to which this is actually desired.
>=20
> One disadvantage (or is it an advantage? I'm never sure) of the fact
> that portmaster does not maintain state between runs is behavior like
> you're seeing here. To answer your question, assuming that everything
> went well with the -o command, there is no reason that portmaster
> would have to build the port again. The -r option needs an up to date
> +REQUIRED_BY, which is a side effect of (re)building it; but the above
> could just as easily be written:
>=20
> portmaster -o www/neon29 www/neon28
> portmaster --check-depends
> portmaster `cat /var/db/pkg/neon29-0.29.3_2/+REQUIRED_BY`
>=20
> I often get the request for this feature (a -r that doesn't rebuild
> the port) but have never found the time to work on it. I'll try to get
> around to it soonish.

Can't this be handled by using -x ? I'm totally confused about how -x
should be used, I don't think I managed to make it do what I thought it
would do more that once or twice. :)

--=20
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B

--Sig_/ipQEiDv=1ZKKLt7gUt_ttk9
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)

iEYEARECAAYFAkxWhn4ACgkQJ7GIuiH/oeWZCACeLtC+i/9DiOrw4cdopHeznNYq
RL8AoIKsT+qCAGKafz+UJEeONfHV4H54
=bcDD
-----END PGP SIGNATURE-----

--Sig_/ipQEiDv=1ZKKLt7gUt_ttk9--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100802114855.1b786820>