From: Eric Sandeen <sandeen@sandeen.net>
To: Greg Freemyer <greg.freemyer@gmail.com>,
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: Mon, 20 Oct 2014 08:54:47 -0500 [thread overview]
Message-ID: <54451427.9060306@sandeen.net> (raw)
In-Reply-To: <30CA1845-C213-49EA-8809-F1E7A98AE7F9@gmail.com>
On 10/20/14 6:55 AM, Greg Freemyer wrote:
> Opensuse is building rpms of 1.1.1 so the build infrastructure isn't
> too badly broken. I don't know if they are following FHS, but I
> doubt they use /opt.
The build works fine, it's the "Makepkgs" that I think is a bit odd,
at least for RPM packaging.
Also, if we really want to encourage packaging, we should probably start
sticking official version numbers on it. "1.1.1" was tagged in Dec 2012,
and there have been no "releases" since.
> The opensuse package/specfile can be found at:
> https://build.opensuse.org/package/show/filesystems/xfstests
>
> The rpms including the source rpm can be downloaded from:
> http://software.opensuse.org/download.html?project=filesystems&package=xfstests
>
> Note the specfile applies a patch to change the install aspect of
> the tarball immediately after untar'ing it.
>
> I don't maintain that so I don't know why the patch is needed.
Ok, cool, I'll take a look at the specfile & patch. I had also packaged
it up for our internal QA use long ago, and had to make a few changes
as well.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-20 13:54 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
2014-10-20 11:55 ` Greg Freemyer
2014-10-20 13:54 ` Eric Sandeen [this message]
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=54451427.9060306@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=greg.freemyer@gmail.com \
--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