Re: cvs commit: ports/astro/orsa Makefile

[ Available lists | Index of cvs-all | Month of Jun 2011 | Week of 17 Jun 2011 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Ion-Mihai Tetcu <itetcu@FreeBSD.org>
Date
17 Jun 2011 08:07:17
Subject
Re: cvs commit: ports/astro/orsa Makefile
Message-ID
20110617110711.3c4f8e3a.itetcu@FreeBSD.org


[ Hide this part ]
On Thu, 16 Jun 2011 19:45:57 -0400
Sahil Tandon <sahil@FreeBSD.org> wrote:

>> Should one wait a day or so before committing the bumps to avoid
>> certain "race" conditions with tinderbox, where it might build the port
>> requiring the dependent before rebuilding the dependent?

No, there is no such race, on regular tindy, QAT (soon to be back) or
pointyhat. You should commit this kind of updates _exactly_after_ you
did the update of the dependency. Waiting hours / days / whatever gets
you pointyhats and agry mails from users unable to run their ports
after your update of the dependency.

Please talk about this with your mentors (cc'ed).

> I believe shlib-related PORTREVISION bumps should be committed right
> away.

Yes. Not the same commit, but exactly after, one commit for all
afftected ports.

Finding affected ports:
- ports that list the lib in question in LIB_DEPENDS
- if the dependency has one of the USE_XXX, all the ports that have
that USE_XXX defined (but take a look at what that USE_XXX actually
does, there might be exceotions)
To be safe:
grep -R libsomthing /usr/ports

This is actually documented in PH. Please take some time to read it
all, even the sections that are not in your usual area of interest.


HTH,

--
Ion-Mihai Tetcu <itetcu@FreeBSD.org>


Elapsed time: 0.129 seconds