#60 run autogen/configure before trying to build RPM
Closed 6 years ago Opened 6 years ago by brianjmurrell.

It would be nice to be able to build from git[hub] projects that are autotools based.

But in some such cases, it could be that the SPEC file is autogenerated by autoconf from a .spec.in file

It would be nice to be able to specify for such a project steps that need to be done after checkout but before looking for a .spec file to build from.


In fact I am having a hard time finding a project with a .spec file and not .spec.in files. It's a lot more prevalent than I thought.

The major problem of this feature request is "how to specify the build requirements". Autotools-based project usually depend on gnulib, , gettext, libtool, automake, help2man, ... but more exotic tools are often also required.

Also the initial step is non-trivial with autotools, sometimes there's just 'autoreconf -vfi' needed, but some project specific ./autogen.sh scripts or ./bootstrap scripts are used. etc. Also note there's a good discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1420540

The major problem of this feature request is "how to specify the build requirements". Autotools-based project usually depend on gnulib, , gettext, libtool, automake, help2man, ... but more exotic tools are often also required.

True enough. Perhaps an additional field in a copr job to be interpreted exactly like a BuildRequires: in a spec file would suffice.

Also the initial step is non-trivial with autotools, sometimes there's just 'autoreconf -vfi' needed, but some project specific ./autogen.sh scripts or ./bootstrap scripts are used. etc.

Indeed. This would be another additional field of "commands" needed to get to the point of having a .spec file ready to use.

Also note there's a good discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1420540

Yes, indeed. I didn't realise that tickets for copr were being tracked in BZ also.

True enough. Perhaps an additional field in a copr job to be interpreted exactly like a BuildRequires: in a spec file would suffice.

When you wrote it this way, there already is such feature; though that's not implemented per-package, but rather per-chroot (I'm not sure whether we do mind), that's: Settings -> chroot "Edit" button -> Packages.

Indeed. This would be another additional field of "commands" needed to get to the point of having a .spec file ready to use.

Right. I'll try to implement this into srpm-tools, if nobody is faster.

Hi,

this feature is now available with SCM source type and 'make srpm' method.

Docs: https://docs.pagure.org/copr.copr/user_documentation.html#scm
Blog post: https://clime.github.io/2017/10/24/COPR-SCM.html#advanced-howto

Thank you for this suggestion

Metadata Update from @clime:
- Issue assigned to clime
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @clime:
- Assignee reset

6 years ago

Login to comment on this ticket.

Metadata