xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: George Dunlap <george.dunlap@eu.citrix.com>,
	Don Slutz <dslutz@verizon.com>,
	xen-devel@lists.xen.org
Cc: Ian Jackson <ian.jackson@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Olaf Hering <olaf@aepfle.de>,
	Ian Campbell <ian.campbell@citrix.com>,
	M A Young <m.a.young@durham.ac.uk>
Subject: Re: [PATCH v2 2/2] Add a "make rpmball" target
Date: Wed, 05 Mar 2014 10:27:38 -0500	[thread overview]
Message-ID: <5317426A.10306@terremark.com> (raw)
In-Reply-To: <5316F82D.702@eu.citrix.com>

On 03/05/14 05:10, George Dunlap wrote:
> On 03/04/2014 08:35 PM, Don Slutz wrote:
>> On 03/04/14 15:23, George Dunlap wrote:
>>> mkdir -p rpm/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
>>
>> That does not work, but:
>>
>>
>> mkdir -p rpm/{BUILD,RPMS,SOURCES,SPEC,SRPMS}
>>
>> does (SPECS is not what you want.)
>
> I'm a bit confused now; your colleague said:
>
> --- Begin Quote ---
>
> s/SPEC/SPECS/ in the above two lines (per the rpm.org site).
> It also fixes Don's problem.
>
> --- End Quote ---
>
> Which sounds like the opposite. :-)
>
> The command I sent you was copied from a CentOS wiki -- was the problem perhaps that the "cat" command below the mkdir was still using "SPEC" instead of "SPECS" (and thus failing there, rather than in the rpmbuild)?
>

Yes.

> Is your version of rpmbuild happy with just the one directory named "SPECS", or would it be better to make all the directories?
>
> I don't have a Centos 5.x system to test it on.
>
> Alternately, we could accept this patch as-is, and then you could post a follow-up fixing it on your system.
>

This patch on top of yours works for me on CentOS 5.10:


diff --git a/tools/misc/mkrpm b/tools/misc/mkrpm
index 88cf13e..fb47b6d 100644
--- a/tools/misc/mkrpm
+++ b/tools/misc/mkrpm
@@ -28,8 +28,8 @@ cd dist
  rm -rf rpm

  # Fill in the rpm boilerplate
-mkdir -p rpm/SPEC
-cat >rpm/SPEC/xen.spec <<EOF
+mkdir -p rpm/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
+cat >rpm/SPECS/xen.spec <<EOF
  Summary: Xen development build, version $version
  Name: xen
  Version: $version
@@ -69,7 +69,7 @@ rm -rf \$RPM_BUILD_ROOT
  EOF

  # Package it up
-rpmbuild --define "_xenroot $xenroot" --define "_topdir $PWD/rpm" -bb rpm/SPEC/xen.spec
+rpmbuild --define "_xenroot $xenroot" --define "_topdir $PWD/rpm" -bb rpm/SPECS/xen.spec

  # Tidy up after ourselves
  mv rpm/RPMS/*/*.rpm .


    -Don Slutz

>  -George
>

  reply	other threads:[~2014-03-05 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 13:56 [PATCH v2 1/2] tools: Use --no-print-directory instead of grep for debball version George Dunlap
2014-03-04 13:56 ` [PATCH v2 2/2] Add a "make rpmball" target George Dunlap
2014-03-04 20:17   ` Don Slutz
2014-03-04 20:23     ` George Dunlap
2014-03-04 20:35       ` Don Slutz
2014-03-05 10:10         ` George Dunlap
2014-03-05 15:27           ` Don Slutz [this message]
2014-03-04 21:29   ` Don Koch
2014-03-06 10:34 ` [PATCH v2 1/2] tools: Use --no-print-directory instead of grep for debball version Tim Deegan

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=5317426A.10306@terremark.com \
    --to=dslutz@verizon.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=m.a.young@durham.ac.uk \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).