On Sunday 2012-02-26 17:46, Ruediger Meier wrote:
On Sunday 26 February 2012, Jan Engelhardt wrote:
On Sunday 2012-02-26 15:10, Ruediger Meier wrote:
Yep, I force the "user" to use unrpm only. Requires: do_not_install_this_but_unrpm No, in my case the src tarball is a "git export" (with lots of build requires) and the destination tarball is a "make dist" tar ball to be used by endusers.
I'm doing all this to release upstream projects doing autoreconf, make check, make distcheck etc. on clean OBS hosted distros.
Noble attempt, but you are leaving the user with more than one distified tarball, whose contents are also dependent upon a particular distro. That reeks of release mismanagement.
Hehe, the only "user" here is the release manager himself. He can compare and test all the distified tarballs to elect exactly one (or none) for the official download site.
However maybe it would be better to not publish these tarball rpms. It's a bit pity that you cant't unpublish just a sub-package or is this possible nowadays?
Wasn't it <publish><disable/></publish> combined with `osc wipebinaries`? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org