On 9/18/06, Chris Weyl <cweyl@xxxxxxxxxxxxxxx> wrote:
Hey all--
Is there a way to determine (aka at a script level) what branches are
not currently legacy? If not, maybe we could put a "current-branches"
file in the common module, with:
[...snip...]
Ok, to follow up to myself, it doesn't appear as if there is any
method in place currently. If I don't hear any screams
(admonishments, swats, "just what do you think you're doing", etc) in
the next day or so, I'll add a file to the common module called
"current-branches" that will be the same as the branches file, except
with only entries for FC-5 and devel.
Using this, and patching a Makefile (upper-level, not in a branch dir)
thus, allows for a build-all command to build all current branches:
--- Makefile 12 Aug 2006 04:06:09 -0000 1.1
+++ Makefile 19 Sep 2006 04:54:28 -0000
@@ -1,4 +1,8 @@
# Top level Makefile for module perl-POE-Component-SSLify
+
+# for target build-all
+BRANCHES := $(shell cat common/current-branches | sed -e 's/:.*//')
+
all : CVS/Root common-update
@cvs update
@@ -8,6 +12,10 @@
common : CVS/Root
@cvs checkout common
+# tag & build all non-dead non-legacy branches
+build-all : common-update
+ @for br in ${BRANCHES} ; do echo Building $$br ; cd $$br &&
test -f dead.package || make tag plague ; cd .. ; done
+
CVS/Root :
@echo "ERROR: This does not look like a CVS checkout" && exit 1
This way such a build target can exist w/o needing to be updated every
time a new release comes out or an old release goes legacy.
-Chris
--
Chris Weyl
Ex astris, scientia
--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list
