rbrownsuse

7 ms·

31.
by rbrownsuse 11y ago
and one question that doesn't get answered by that link - yes, we properly separate non-free software from our free packages
32.
by rbrownsuse 11y ago
We do automated testing from our 'traditional' distributions, including versions that existed BEFORE Tumbleweed in it's current form..like 13.1, 12.3, etc.. So in that case, we're going back years ;)
33.
by rbrownsuse 11y ago
I wrote a rather long mailinglist post that should answer a lot of those questions.. https://lists.opensuse.org/opensuse-project/2016-02/msg00003...
34.
by rbrownsuse 11y ago
Yes, the open build service takes care of that for you You don't need to tell Foo about your package, the build service will detect those relationships If you build against Foo, and Foo changes, the OBS will rebuild your package for yo
35.
by rbrownsuse 11y ago
You'd be surprised how little a problem it is in the real world In the case of UI changes, openQA can have it's 'needles' updated in it's webUI. Look at the new screenshot, compare to the old screenshot, tell openQA
36.
by rbrownsuse 11y ago
zypper takes care of most of that for us - it really is an exceptional package manager We have some tests in openQA that keep an eye on upgrades, as well as some users who like to stagger their Tumbleweed updates for some weeks. I think the
37.
by rbrownsuse 11y ago
Apart from Debian Sid: has no testing, but Tumbleweed does - so those breakages don't happen
38.
by rbrownsuse 11y ago
It's probably worth mentioning that the openSUSE Build Service pretty much fills the same role as AUR http://software.opensuse.org lets you search across all the available repositories and easily install packages on your Tu
39.
Why You Should Use Tumbleweed(rootco.de)
123 points by rbrownsuse 11y ago|66 comments
40.
Why should anyone be interested in openSUSE?(sysrich.co.uk)
1 points by rbrownsuse 12y ago|0 comments