I\'m trying to build my own rpm package and have a couple of doubts. First of all, in several places I\'ve red that one shouldn\'t build rpms as root. Why is that? During the building process, rpmbui
I am trying to build my first rpm package, which is one simple executable (mysh). My spec file: Summary: bla <br>
Not sure if this is the right place to post the question. I am trying to create rpm\'s for my project, this is the first time I am writing a spec file. When I am building the spec the file with the co
My goal is to come up with a spec file that defines subpackages dynamically. Currently, I have a macro defined in the spec file so that I can call it with different parameters to generate different %
I\'m working on a spec file (foo.spec) that, when built, results in two RPMs: foo-1-1.i386.rpm (the main program) and libfoo-1-1.i386.rpm (the required library files). The foo.spec file states that fo
I have some problems with an rpm spec file that is listing the same file multiple times. For this spec we do some normal compilation and then we have script that copies everything to the buildroot. Wi
Summary: A small lighttpd Name: lighttpd Version: 1.4.28 Release: 1000 License: LGPL Group: Applications/Webserver
I\'m trying to create an RPM of my package, which is built using automake and libtool, and I\'ve encountered a problem: rpmbuild aborts upon discovering that the installed programs of the package cont
I have a customized RPM that builds a set of subpackages. Each subpackage has a %post script in the spec file that is used to copy some symlinks to another folder:
deb: fakeroot dpkb-build -b directory pack开发者_JAVA百科age.deb # Name, version, architecture, etc. are in directory/DEBIAN/control