Mailinglist Archive: opensuse-buildservice (206 mails)

< Previous Next >
Re: [opensuse-marketing] Re: [opensuse-buildservice] Proposed OBS rename / + BRETZN name
On Wed, Feb 2, 2011 at 2:52 PM, Jos Poortvliet <jospoortvliet@xxxxxxxxx> wrote:
That reads as if you assume OBS is not successful.  I feel the opposite.

Indeed. It is popular but could be more so ;-)

BTW we also need to do more in the area of USING those huge numbers. For
marketing but also community building purposes. How could we get the tens of
thousands who use OBS to contribute to openSUSE? After all, they're VERY close
to openSUSE already - it's just pushing a few buttons to submit their packages
to factory or request merges with existing packages to fix bugs.

I don't think it is necessarily that simple.

First, I _assume_ lots of those 100+K packages are the same package
just in lots of repos.

For instance each of the main packages is probably in at least a devel
package, factory, 11.3, 11.2, 11.1 discontinued. Admittedly, each of
those may be at a different version level/patch level. But 100+K
packages is a highly misleading number I suspect.

And then for lots of smaller packages, I don't think they are really
built for distro use.

First, many don't have man pages for executables, which I think is
required in the push to factory.

Another example is open2300. I packaged it because I use it, but it
generates a dozen or so executables. All *2300 (open2300, log2300,
etc.). I can't envision putting that in factory that way. The names
really need to be changed to 2300* (2300open, 2300log, etc), but the
upstream project is basically dead, so I don't see it happening there.

I may get it into the distro eventually, but for now I'm happy with it
in a devel project. So OBS for open2300 is giving me exactly what I
want. A way to publish a little known/used app without the more
formal requirements appropriate to a full distro release.

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups