tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: bulk builds and failed packages



It looks like www/ap-php is the cause for all of the different php and apache versions. I only explicitly have www/apache24 in limited_list.

On Tue, 21 Apr 2015, David Brownlee wrote:

On 21 April 2015 at 12:05, Jared McNeill <jmcneill%invisible.ca@localhost> wrote:
On Tue, 21 Apr 2015, David Brownlee wrote:

Rsync the old package dir to the new before building, then run a
cleanup pass to remove older revisions of the same package after
build? (assumes you can fit two copies on the target :)

What would the cleanup pass look like? It seems like it would get
complicated when more than one version of a package is meant to exist, like
apache-2.2.29 and apache-2.4.12. Say apache-2.2.29 is bumped to nb1, and
then fails to build -- how do I know to fallback to 2.2.29 instead of
2.4.12?

Given you mentioned limited numbers of packages I'd not considered
multiple apache-* packages being built.. :/, though there would
probably be some magic possible with the bulk build report,
particularly if you kept the previous one's report to provide its
directory to pkg name mapping...



Home | Main Index | Thread Index | Old Index