-----BEGIN PGP SIGNED MESSAGE-----
On 03/31/2011 03:32 PM, Michal Marek wrote:
On 31.3.2011 16:53, Jeff Mahoney wrote:
I like the idea. We don't ever modify those
patches -- if we did, we're
doing something wrong.
The down side is that replacing the entire
tarball means that the OBS
project gets a new tarball every time we do an -rc or -stable bump.
Hm, right, I didn't think of that.
That's time consuming when syncing the
project. If we could work it so
that it uses the incremental patches, that would be perfect.
Automatically generating incremental patches would be tricky (and also
too much script bloat for a relatively little gain...). But it should
be possible to eliminate uploading the upstream tarball completely if we
can use "source services":
No, I don't mean we generate our own. That would be a big pain. Our
patch-2.6.xx-rcy patches aren't generated by us. Upstream does that
already. They're from
. As far as I understand, it is possible to upload a small xml file
instead that contains the url of the tarball to download.
Anyway, could you try the tarball method when you update to 2.6.39-rcX?
A couple of more linux tarballs will surely not kill the buildservice.
I'll look into the source service thing in parallel.
Sure. That'll work with mbuild for now too, right? It picks up whatever
we throw in that variable.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org