2011/12/23 Michael Schroeder
On Fri, Dec 23, 2011 at 03:15:48PM +0000, Nelson Marques wrote:
Let me see if I understood this correctly:
* I want to package foobar-1.0.tar.xz; (upstream releases only .xz) * I have to introduce: "BuildRequires: xz"
Yes.
Sure.
* I have to waste time introducing references to why I have to include a "BuildRequires: xz"
No.
Next time I'm asked to do so, package gets orphaned right on that moment.
* I have to increase the size and the complexity of the spec file;
You seriously think that BuildRequires is complex?
Yes, it should be a part of the build environment. It's not a build dependency.
* I have to spend extra time referencing more stuff in the changelog;
No.
Next time I don't get a package accepted because of it, it gets orphaned right on the very same moment.
In the end... 'xz' which you don't add to the build environment is still installed. Where is exactly the gain you try to point here? (besides the fact that you deliberally are increasing the maintenance time of my package)
Please demonstrate how my package is built faster by not having xz installed on the build environment by default (but is installed still).
This is not about your package, other packages that don't need xz will be built faster. With your logic, we should also install Xorg, an ocaml compiler, a jave compiler and so on, because some package might need it.
You can give all the examples you want, you are still failing to realize XZ is used to unpack the source code and not to build the application. That's probably why it _should_ be a part of the build environment. Please, whats the difference between gzip, bunzip and xz ? Why are they treated differently ?
Let me guess... for your own pleasure and to support idea you preach, I probably have still to spend more time unpacking and repacking the sources in bz2 or gz ? :)
No! Do *not* repackage the sources! Just add that BuildRequires line.
Why? using your logic, if I repackage the sources with bunzip, it gets built faster! Afterall you don't install .xz and you save precious time there :)
My brain is probably going through a meltdown, because all I can see in this is mainly: "increase the load on the packagers". And it's nice that now I have to reference a few incidents on bugzilla so I can produce comments to go with the buildrequirements that aren't really "Build Requirements" and should be part of the build environment...
Wtf? As I said, that bugzilla reference is for *released* products, not Factory. You're talking about a new package or a new version.
I'm talking about packages and development repo's, updates mainly. I'm a puppet maintainer, I'm allowed to maintain packages on low profile repositories and hammer them in the way I want, but I'm not allowed to maintain the same packages on the official development repository, so I might get my packages declined. Considering that everyone is placing good efforts in killing volunteer contributions, I can see a good ammount of packages becoming orphaned :)
If upstream projects are moving to .xz (not just GNOME, but also many which have huge tarballs), what do we earn here ? Another thing that pops up is that this option will probably increase the load in other areas, for example network traffic because a 100Mb source in bz2 is most likely around 70Mb in .xz.
No, 'cause you should not repackage.
Good. Sounds like a Mexican standout :) This generates orphaned packages.
Cheers, Michael.
-- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-- Nelson Marques /* http://www.marques.so nmo.marques@gmail.com */ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org