[opensuse-buildservice] Solving source service misconceptions
Hi y'all, as it occured several times already, there seem to be some misconceptions about source services for the Build Service. Recently, it seemed to became fashionable to replace each and every package tarball with a download service pointing to some URL. As by most commit messages, people seem to be believe that some magic update logic will happen once upstream releases a new tarball. Just to make this clear, this won't happen! The only thing that changes is that the source tarball is not stored alongside your spec but downloaded on-demand instead (speak, with every rebuild). And it is not (yet) cached and you still have to update stuff (by changing that URL). As a packager, you have to download the tarball anyways because you want to look at new documentation files or update your local patches. However, this may make sense if you use it together with some more source services (like re-packaging or checksum checks), but I consider it unfriendly to change someone else's packages to use source services without asking. Please don't do that. -- Mit freundlichen Grüßen, Sascha Peilicke http://saschpe.wordpress.com
Am Montag, 21. März 2011, 09:19:06 schrieb Sascha Peilicke:
Hi y'all,
as it occured several times already, there seem to be some misconceptions about source services for the Build Service. Recently, it seemed to became fashionable to replace each and every package tarball with a download service pointing to some URL. As by most commit messages, people seem to be believe that some magic update logic will happen once upstream releases a new tarball. Just to make this clear, this won't happen!
The only thing that changes is that the source tarball is not stored alongside your spec but downloaded on-demand instead (speak, with every rebuild). And it
with every local rebuild (unless you use --no-service or --noinit switch). The server side rebuilds don't re-download it.
is not (yet) cached and you still have to update stuff (by changing that URL). As a packager, you have to download the tarball anyways because you want to look at new documentation files or update your local patches.
However, this may make sense if you use it together with some more source services (like re-packaging or checksum checks), but I consider it unfriendly to change someone else's packages to use source services without asking. Please don't do that.
IMHO we require to build up trust in the used source files we use. Just started a discussion regarding this on opensuse-factory mailing list. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Mar 21, 2011 at 5:43 AM, Adrian Schröter <adrian@suse.de> wrote:
Am Montag, 21. März 2011, 09:19:06 schrieb Sascha Peilicke:
Hi y'all,
as it occured several times already, there seem to be some misconceptions about source services for the Build Service. Recently, it seemed to became fashionable to replace each and every package tarball with a download service pointing to some URL. As by most commit messages, people seem to be believe that some magic update logic will happen once upstream releases a new tarball. Just to make this clear, this won't happen!
The only thing that changes is that the source tarball is not stored alongside your spec but downloaded on-demand instead (speak, with every rebuild). And it
with every local rebuild (unless you use --no-service or --noinit switch). The server side rebuilds don't re-download it.
So pointing a service on OBS at a nightly build url won't cause it to download when that tarball is updated? I did set one of those up last week, but I haven't had a chance to go back and see if it worked the way I expected. Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter -
Greg Freemyer -
Sascha Peilicke