On Fri, Nov 20, 2009 at 12:49:30PM -0600, Dennis Gilmore wrote:
> 
> > This is rubbish. Spacewalk repos are the upstream for whatever makes
> > it into Fedora and EPEL. Why on Earth should upstream stop building
> > and releasing their packages just because someone has decided to
> > put those packages to Fedora or EPEL?
>
> Because thats what we said we were going to do at the start of this
> whole thing.  typically upstreams only ship tarballs.  the goal was to

Currently, we don't even have a way (tooling + infrastructure) to
only ship tarballs, list tarballs, etc. In addition, our development
and testing setups consist of RHELs and Fedoras. If I commit a change
to the git repository and I want to test that change, I need an rpm,
not tarball.

> move everything into fedora/epel and stop building and shipping the
> spacewalk repos.

Even if all our packages were in Fedora today, we still need a way
to build packages and create repos of those packages. Fedora 11 might
have Spacewalk 0.6 packages in it and when we release Spacewalk 0.7,
we might not want to destabilize those F11 installations by rushing
it all to F11 immediatelly. But we will still need a repo to install
that Spacewalk 0.7 on F11 to check for regressions.

What we might consider doing is actually yet another split, of both
the server and the client packages. One repository which would only
contain packages that are not in Fedora / EPEL, and one repository
containing a bleeding edge of all packages where we are upstream.

So, for example, since nocpulse-common made it to Fedora and is in
F12, we probably should not have the rpm in Spacewalk 0.7 yum
repository for Fedora, once we do 0.7 release. It should be fairly
easy to do with the "supporting" packages, even if we'll have to take
extra care to play nice with older versions of these supporting
packages in our main application code (spacewalk-java,
spacewalk-backend, etc.).

But there has to be a yum repository with all our packages (those
that we are upstream of) in latest versions, both for internal and
external testing, so that people have a way to install the latest
software.

-- 
Jan Pazdziora | adelton at #satellite*, #brno
Satellite Engineering, Red Hat

_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to