public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Bill Nottingham <notting@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: makefile update to properly grab makefile.common
Date: Tue, 11 Aug 2026 10:33:32 GMT [thread overview]
Message-ID: <178644441216.1.5880546806686530584.rpms-glib2-2880db3befab@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 2880db3befab69d13dee89de5e3a2e1b4f873e7a
Author : Bill Nottingham <notting@fedoraproject.org>
Date : 2007-10-15T18:47:38+00:00
Stats : +17/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/glib2/c/2880db3befab69d13dee89de5e3a2e1b4f873e7a?branch=cve-2026-58016-f44
Log:
makefile update to properly grab makefile.common
---
diff --git a/Makefile b/Makefile
index 1a9187a..dd6bad4 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,21 @@
# Makefile for source rpm: glib2
-# $Id: Makefile,v 1.1 2004/08/31 10:08:53 cvsdist Exp $
+# $Id: Makefile,v 1.2 2005/11/15 18:51:53 mclasen Exp $
NAME := glib2
SPECFILE = $(firstword $(wildcard *.spec))
-include ../common/Makefile.common
+define find-makefile-common
+for d in common ../common ../../common ; do if [ -f $$d/Makefile.common ] ; then if [ -f $$d/CVS/Root -a -w $$/Makefile.common ] ; then cd $$d ; cvs -Q update ; fi ; echo "$$d/Makefile.common" ; break ; fi ; done
+endef
+
+MAKEFILE_COMMON := $(shell $(find-makefile-common))
+
+ifeq ($(MAKEFILE_COMMON),)
+# attempt a checkout
+define checkout-makefile-common
+test -f CVS/Root && { cvs -Q -d $$(cat CVS/Root) checkout common && echo "common/Makefile.common" ; } || { echo "ERROR: I can't figure out how to checkout the 'common' module." ; exit -1 ; } >&2
+endef
+
+MAKEFILE_COMMON := $(shell $(checkout-makefile-common))
+endif
+
+include $(MAKEFILE_COMMON)
reply other threads:[~2026-08-11 10:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178644441216.1.5880546806686530584.rpms-glib2-2880db3befab@fedoraproject.org \
--to=notting@fedoraproject.org \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox