-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.00.0912061917360.7514@nimrodel.valinor> On Sunday, 2009-12-06 at 18:52 +0100, Lars Müller wrote:
On Sun, Dec 06, 2009 at 05:23:24PM +0100, Carlos E. R. wrote:
Absolutely false.
Have you ever tried it?
No way.
I, we, don't intend to make rpms to be used by others, they are private. We can not use a public buildservice, even if we knew how to use it.
Please read my last mail again. In particular the end.
The openSUSE Build Service (OBS) and in particular the osc build feature doesn't force anyone to pusblish anything.
There isn't anything which forces you to publish the build results to the public. You build on your local system inside a clean chroot setup.
With no internet connection, and no need to log into your servers?
But the OBS and the osc command in particular enabled you to build software in an easy and secure way. Please give it a try!
Document it. For absolute newbies, no knowledge of how to package, no knowledge of how to create the spec file - and no intention to create it manually. Does osc create the spec file on the fly, same as checkinstall does?
And if you like you're even able to share software packages you created by this means and to contribute to any of the projects using the OBS infrastructure.
No.
If checkinstall is broken, just repair it!
I expect those needing and using it will even repair it. If not we're here at the very same point as with the sax2 discussion.
I'm not a dev. You are my software suplier, please repair it for me.
Have you read any of the available documentation?
I need no documentation to use checkinstall.
http://lizards.opensuse.org/2009/09/13/build-service-intro/ might be a good starting point.
Before any further replies please read the available articles.
### OBS intro quote start Build Service Intro Sunday, September 13th, 2009 by Andreas Jaeger
I stumbled upon a little series of articles at the LinuxFoundation Developer Network explaining the openSUSE Build Service.
The articles are:
* openSUSE Build System: Building Binary Packages for Many Linux Distributions at Once http://ldn.linuxfoundation.org/article/opensuse-build-system-building-binary...
* openSUSE Build System: Building RPM Packages http://ldn.linuxfoundation.org/article/opensuse-build-system-building-rpm-pa...
] Downloading the siproxd tarball, extracting it, and then uploading the ] spec file from the desktop machine got the build going. Soon after the ] spec file was uploaded the status for Fedora and openSUSE became ] "scheduled." The OBS i What process creates automatically that spec file? How many times do I have to tell you that I'm not a developper nor a packager? That I have no idea, no time to learn, and no inclination whatsoever, on how to create an spec file? I need an automated process. Fully automatic. Checkinstall. Gosh! Like talking to deaf people. :-/ - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAksb91IACgkQtTMYHG2NR9X1swCfQtyYapXEGHJ4TZaUXcbUAzoQ NQsAnRCDsFXJ1Gp6oQVlcxU6PKvzMj95 =I8e5 -----END PGP SIGNATURE-----