http://bugzilla.suse.com/show_bug.cgi?id=954697
http://bugzilla.suse.com/show_bug.cgi?id=954697#c4
Richard Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
Flags|needinfo?(rbrown@suse.com), |
|needinfo?(coolo@suse.com) |
--- Comment #4 from Richard Brown ---
This bug is full of invalid statements and assumptions
Lets start with the biggest one
The Tumbleweed Rolling Distribution is ONLY the repositories in
http://download.opensuse.org/tumbleweed/repo/ and ONLY the media in
http://download.opensuse.org/tumbleweed/iso/
These contain software which has been reviewed, integrated, built, and tested
as a single cohesive distribution. This process is clearly documented:
https://en.opensuse.org/openSUSE:Factory_development_model
Any other repository, from any other source, even if it's built for Tumbleweed,
results in a system that is NOT Tumbleweed, but a custom Tumbleweed+Something
that is _NOT_ reviewed, _NOT_ integrated, _NOT_ tested, and _NOT_ built as a
single cohesive distribution
It _MAY_ work, when it does, great, but saying that Tumbleweed is a lie because
stuff in unsupported, unofficial repositories is broken is just plain wrong
Now, a few other things to clear up
'snapshot' in OBS is _NOT_ the published Tumbleweed snapshot in
http://download.opensuse.org/tumbleweed/repo/. Therefore there is room for
breakage if people are building against "snapshot" OR "standard", because in
both cases they can drift from what is published as a Tumbleweed snapshot. This
is a known issue with OBS, which has been reported. But until then, there is
room for failure
But, that still doesn't make this bug or the points you make valid. Even if
when this OBS issue is fixed, there is no formal review process for the
packages in other repos. There is no testing of packages in other repos. The
quality is always questionable
And Even if the Repo is well maintained, and carefully tested and reviewed by
their individual maintainers, there are still fundemental risks, because
package FOO in Repository A can easily have its libraries/API/ABI broken by
package BAR from Repository B.
The only way of being sure that everything works together properly, is by
building it together properly - which means following
https://en.opensuse.org/openSUSE:Factory_development_model
If repository maintainers want their software to be used in Tumbleweed, the
best way for them to do that is by SUBMITTING IT TO FACTORY
Anything else is going to result in something which is less tested, not
reviewed, not integrated, and cannot be guaranteed to work even if it does
build.
--
You are receiving this mail because:
You are on the CC list for the bug.