From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>, "Kaul, Yaniv" <Yaniv.Kaul@emc.com>
Cc: esandeen@redhat.com, fstests@vger.kernel.org,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Can't build RPM of xfstests
Date: Sun, 19 Oct 2014 22:35:47 -0500 [thread overview]
Message-ID: <54448313.7040602@sandeen.net> (raw)
In-Reply-To: <20141020014750.GL7169@dastard>
On 10/19/14 8:47 PM, Dave Chinner wrote:
> [ cc fstests@vger.kernel.org ]
...
>> === rpm ===
>> /bin/sed -e's|@pkg_name@|xfstests|g' \
>> -e's|@pkg_version@|1.1.1|g' \
>> -e's|@pkg_release@|1|g' \
>> -e's|@pkg_distribution@|Linux|g' \
>> -e's|@build_root@|/tmp/34943|g' \
>> -e'/^BuildRoot: *$/d' \
>> -e's|@make@|/usr/bin/gmake|g' < xfstests.spec.in > xfstests.spec
>> /usr/bin/rpmbuild -ba --rcfile ./rpm-4.rc xfstests.spec
>> error: File /root/rpmbuild/SOURCES/xfstests-1.1.1.src.tar.gz: No such file or directory
>> gmake[1]: *** [dist] Error 1
>
> I've never tried to build xfstests packages, so I'd make the
> assumption that the package build infrastructure is broken and needs
> fixing. That's looking for the tarball in the wrong place. My naive
> reading of that is rpmbuild is expecting to run as root, not as a
> jenkins user....
>
> Eric, you're the local RPM expert - any ideas?
>
> FWIW, I'll take whatever patches you guys come up with that make it
> build rpms properly. ;)
xfstests rpms have just never been a priority for me. I run it just fine out
of a checked-out git repo, and it doesn't require installation; on the other
hand, making it palatable for a proper FHS-compliant distro package would
require a fair bit of restructuring beyond just the packaging scripts.
And... I honestly have no idea how the Makepkgs stuff is supposed to work.
I've never been a fan of upstream containing packaging bits anyway; different
distros have different requirements, and the Makepkgs script has always seemed
weird. RPM/specfiles are supposed to drive the build - the build isn't supposed
to drive rpm. I think it'd be best to make a distro-specific specfile which knows how
to handle an xfstests tarball. Trying to reverse engineer Makepkgs doesn't sound
fun to me; rpmbuild knows how to do this stuff. Dropping a generic RPM specfile
into the top level dir would probably be enough to get it off the ground even if
it doesn't conform to any particular distro's packaging rules.
I think it's up to those who want rpms to dig into this, for now. Dumping all
files into /opt/xfstests is probably simplest, since FHS-compliance is probably a
long ways off.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-20 3:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 6:58 Can't build RPM of xfstests Kaul, Yaniv
2014-10-20 1:47 ` Dave Chinner
2014-10-20 3:35 ` Eric Sandeen [this message]
2014-10-20 11:55 ` Greg Freemyer
2014-10-20 13:54 ` Eric Sandeen
2014-10-20 23:08 ` Dave Chinner
2014-10-20 23:31 ` Greg Freemyer
2014-10-20 23:57 ` Dave Chinner
2014-10-21 3:15 ` Eryu Guan
2014-10-20 23:23 ` Eric Sandeen
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=54448313.7040602@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Yaniv.Kaul@emc.com \
--cc=david@fromorbit.com \
--cc=esandeen@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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