Re: [opensuse] Simple source rpm as an example
TMF Netherlands B.V. Corporate ICT / Team UX
Greg Freemyer
04/06/09 7:08 PM >>> Thanks,
I do appreciate the above, but using the OBS is just not comparable to ./configure; make; make install (assuming it works).
I'm installing a relatively small program that did not come with a specfile.
I did not have compilers etc. installed on my laptop, so I decided to give the OBS a shot and build a real rpm.
The INSTALL file that came with the source could have been followed in short order to get the package installed manually.
Doing it via the OBS has taken me hours of trial and error and a few questions on the OBS mailing list.
For your typical OpenSUSE user that just wants to compile a package and install it, the OBS is just not ready.
In this case I'm not sure if building an RPM is the best thing to do anyhow. Follw up on http://en.opensuse.org/Build_Service#Advantages : OBS is interesting for an end user in this respect: * Always get the newest software versions for their distribution. Using a trust relationship in the build service, the user can declare "I trust the Project xy" and can afterwards install packages only from this project. * Getting upgrades for older distributions. (Like getting a new KDE 3.5.7 for SL 10.0) * More unification between the different distributions. Packages from the build service can bring people together - thinking about "Why do they do such things? Why do they use these directories? - I want to get it for my distribution, too". (But this is something for the future... :-) I do really not think that every user should replace his 'traditional' package installation from source by injecting the source into OBS. The goal of OBS is to have some more skilled users (and users that want to be more skilled) provide binary packages to everybody. Compiling them in a central place and offering them. You're already a big step further than 'Joe Average': He wants to download and 'install' the package by double clicking at best (we get close to that with 1-click-installer'). As written before: for creating a working spec file you first need to understand the 3-step-install outlined in all INSTALL files. (and to answer the question for your docs: %doc will be the macro to be used in the %files section). Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks all for the feedback.
I have my first package fully building and the docs getting put into
the share/packages directory appropriately.
OpenSUSE and Fedora seem to be working fine.
Greg
On Mon, Apr 6, 2009 at 4:32 PM, Dominique Leuenberger
TMF Netherlands B.V. Corporate ICT / Team UX
Greg Freemyer
04/06/09 7:08 PM >>> Thanks,
I do appreciate the above, but using the OBS is just not comparable to ./configure; make; make install (assuming it works).
I'm installing a relatively small program that did not come with a specfile.
I did not have compilers etc. installed on my laptop, so I decided to give the OBS a shot and build a real rpm.
The INSTALL file that came with the source could have been followed in short order to get the package installed manually.
Doing it via the OBS has taken me hours of trial and error and a few questions on the OBS mailing list.
For your typical OpenSUSE user that just wants to compile a package and install it, the OBS is just not ready.
In this case I'm not sure if building an RPM is the best thing to do anyhow. Follw up on http://en.opensuse.org/Build_Service#Advantages : OBS is interesting for an end user in this respect: * Always get the newest software versions for their distribution. Using a trust relationship in the build service, the user can declare "I trust the Project xy" and can afterwards install packages only from this project.
* Getting upgrades for older distributions. (Like getting a new KDE 3.5.7 for SL 10.0)
* More unification between the different distributions. Packages from the build service can bring people together - thinking about "Why do they do such things? Why do they use these directories? - I want to get it for my distribution, too". (But this is something for the future... :-)
I do really not think that every user should replace his 'traditional' package installation from source by injecting the source into OBS. The goal of OBS is to have some more skilled users (and users that want to be more skilled) provide binary packages to everybody. Compiling them in a central place and offering them.
You're already a big step further than 'Joe Average': He wants to download and 'install' the package by double clicking at best (we get close to that with 1-click-installer').
As written before: for creating a working spec file you first need to understand the 3-step-install outlined in all INSTALL files.
(and to answer the question for your docs: %doc will be the macro to be used in the %files section).
Dominique
-- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Dominique Leuenberger
-
Greg Freemyer