Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[vdb]

I'm experimenting a bit with building an rpm file to keep aMule as I have compiled it now. However, when I use the amule.spec file I keep getting a build error: "/usr/bin/amuled installed but not packaged". Oddly I don't have amuled in /usr/bin, but in /usr/local/bin, but I guess the path setting picks it up nevertheless.

I reckon it's because in the amule.spec file it actually instructs to install these files, am I correct in this? And since I already have amuled installed, this will fail.

Question: Can I simply remove all the lines using _bindir? Will then the rpm still be produced?

As you can see I'm a new at this, and the since it takes just over 2 hours every compilation run I hope somebody can give me some useful pointers here.

[IhmSelbst]

since you enabled the daemon by --enable-amule-daemon in the ./configure-section, this requires an entry %{_bindir}/amuled.
the %{_bindir}/whatever-lines tell it, which executables should be installed. (so, you shouldn´t remove them for that reason.)
you can change the install-path, too, for example by using --prefix=/usr flag, to install in /usr


cu

[vdb]

Of course, that's it, I added the daemon and the remote GUI to the compile options, but not to the install section, hence it rpmbuild complains that it has something installed but not packaged.

Thanks for this, I'll try it right away this afternoon.

[stefanero]

btw cool feature for slow mashines --> ccache