On Wed, Sep 16, 2009 at 6:57 PM, Jussi Lehtola <jussilehtola@xxxxxxxxxxxxxxxxx> wrote: > On Wed, 2009-09-16 at 19:15 +0000, Valent Turkovic wrote: >> On Wed, 09 Sep 2009 09:52:09 -0400, Todd Zullinger wrote: >> >> > There is a nice document on the Fedora wiki describing the process: >> > >> > http://fedoraproject.org/wiki/How_to_create_an_RPM_package >> >> This is far, far from simple page :( > > Then have a look at the Gurulabs howto > > http://www.gurulabs.com/GURULABS-RPM-LAB/GURULABS-RPM-GUIDE-v1.0.PDF > > which I find quite nice. You'll be wanting to look at page 18 of the PDF > (on the page it reads 12-17), which handles spec files. > -- > Jussi Lehtola > Fedora Project Contributor > jussilehtola@xxxxxxxxxxxxxxxxx > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > It is just RIDICULOUS not to have an automated way to create RPMs. If I can download some source file, and then ./configure make and make install, this automated tool is perfectly capable of finding the base system, the files installed during the process, and the requirements. I just don't understand this *nix attitude that "complex is good". End users might want to create their own RPMs, too. FC -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
