On 11/02/2016 10:46 AM, James Hogarth wrote:
On 2 November 2016 at 16:37, jd1008 <jd1008@xxxxxxxxx> wrote:
On 11/02/2016 10:08 AM, stan wrote:
On Wed, 02 Nov 2016 10:00:13 +0000
arnaud gaboury <arnaud.gaboury@xxxxxxxxx> wrote:
I am writing a .spec file to build my own .rpm.
Here it is, non completed:
[snip]
RPM build errors:
Empty %files file
/home/makerpm/build_package/mattermost/platform-master/debugfiles.list
Could not execute local: Non zero exit
------------------------------------------
My %files section is indeed empty as I did not finished writing
the .spec file.
Shall I overcome for now this error and consider my local build test
as successful ?
I am not knowledgeable about spec files, but I would say yes. However,
this question seems more likely to get a good answer on the devel list,
where all the packagers hang out.
I was hoping someone would point to an interactive tool for building a .spec
file; or better yet, a gui util.
That would really enable a lot of people, not just the developers.
The templates, macros and Fedora Guidelines documentation do make it a
lot cleaner and simpler than it was 5-10 years back though...
This was something I wrote about building RPMs that should be
applicable - and never forget it's always best to build in mock to
ensure a clean build environment
https://www.hogarthuk.com/?q=node/11
Thanx.
Reason I mentioned "interactive" or "gui" is because many people see the
sheer volume
of things to read AND REMEMBER in order to produce the simplest of .spec
files.
A util that will, for example, scan the source files and ask intelligent
questions that the
user could answer. Among them might be something like:
what is the name and version of the package, that provides header file
abcde.h ?
Of course, some of the needed packages can be discerned by the util by
running the rpm command
to examine all installed packages and what they provide - or even query
the repo by using the
query "provides".
Such a smart app would go a very very long way to speed up the creation
of a spec file.
Cheers,
JD
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
