So Tumbleweed is, I think, almost 2 years old now. It seems to be
working fairly well, or at least well enough for my daily use, and I
haven’t heard any complaints about it in a long time which means that
either no one is using it, or it’s working for others
Anyway, with the advent of 12.3 soon, I have been thinking if Tumbleweed
needed to change any to make things work better.
My original set of complaints a year or so ago about OBS issues that
keep us having a “proper” rolling distribution, still pretty much are
the same:
the build-number issue
build speed
dependancy rebuild problems.
Build speed of OBS has increased recently, I don’t know if it’s just my
imagination, or if I have a higher priority for my repos now, or if new
hardware really was added to the build system, but I’m happy things seem
to be working better in that area at the moment.
But the other two issues are still big ones, as the recent GNOME update
in Tumbleweed proved quite well.
So, I was thinking about maybe, when 12.3 changing Tumbleweed from being
an “add-on” repo on top of the 12.3 repos, to being a “full” distro
snapshot. That would resolve the build number problems we have had, but
the dependancy rebuild issue would increase.
The rebuild problem can be manually handled, much like FACTORY currently
is, but odds are, I would lean toward the conservative side, having more
rebuilds than are probably necessary just to ensure that systems work
well. That means that libreoffice would be updated on a weekly basis
for users, which might get annoying over time
Any thoughts by anyone about this? Or should I just do it and see how
well it works out?
So Tumbleweed is, I think, almost 2 years old now. It seems to be
working fairly well, or at least well enough for my daily use, and I
haven’t heard any complaints about it in a long time which means that
either no one is using it, or it’s working for others
dd
I’using tumbleweed, the rants are almost the same as others linuxes…
for the rest I don’t know anything about the differences between full distro or on 12.3… wi will see, thanks for the great work greg…
Er where did you get that idea from? You do realize that Tumbleweed is maintained by one guy who probably has a day job, or haven’t you used it?
At the moment it’s one tumbleweed repo + standard repos. The standard Oss, Non-oss repos contain standard Gnome, KDE, LibreOffice, etc releases.
I would imagine once you have made the initial install from the 12.x standard repos, you will continue to update from tumbleweed repo (contains updated versions of Gnome, KDE, LibreOffice, etc) + standard Update repos. When 12.x+1 release arrives, then upgrades/downgrades/additions/removals to reach it will come through the tumbleweed repo plus standard Update repos, and the cycle continues.
That’s how I expect it to work having read @dd’s link and expanding mailing list thread. If not someone will put me straight.
No, my change to the way Tumbleweed would be in the future would be that there would be a oss and non-oss repo for Tumbleweed, and you don’t use any 12.3 repo on your machine at all, the Tumbleweed repos would start out being a straight copy of the 12.3 release, but then be updated over time with new updates to the individual packages.
This would make Tumbleweed a full stand-alone copy of the distro, no need to use 12.3 or anything else at all.
Thanks, almost straight now. So no Update repos and no patches/delta package updates (save traffic and time) for us, there all applied by you to the tumbleweed oss and non-oss repos, right?
Thanks, almost straight now :). So no “Update” repos and no security patches/delta package updates (save traffic and time) for us, those all applied by you to the tumbleweed oss and non-oss repos, right?
With this change, I might start using Tumbleweed on at least one machine.
There was a suggestion about 6 months ago (on the factory mailing list, I think), that opensuse releases should be Tumbleweed snapshots, instead of factory snapshots. I thought that an interesting suggestion, and your proposal might be a first step in that direction.
If we move to your proposed system it would be ideal if we could keep everything contained within the Tumbleweed repository.
For my purposes the only reason why i have this repo enabled is because i use the following apps, which aren’t in the main Tumbleweed repository:
Dropbox (not requiring nautilus) - Is in Factory
Homerun (fullscreen KDE launcher) - Looks like it failed to build in Tumbleweed?
Lucky Backup - Is in Factory
I accept that not every app known to mankind can be in Tumbleweed, but my understanding is that Tumbleweed includes a number of applications not found in the standard stable release repos? Needless to say that i don’t want to add to the task of maintaining Tumbleweed.
BTW i’ve been using Tumbleweed for about a year. Really happy with it - reminds me of Linux Mint Debian Edition, but more stable and controlled.
Why not, Tumbleweed has proved its stability through 11.x and 12.x while being more up to date than the standard release.
The future for openSUSE could be an Axis of Good: Tumbleweed, → its snapshot for openSUSE release, → Evergreen for longer-term support. Oh, and the relatively unstable Factory as the 4th dimension, for the “headbangers”.
On Tue, 05 Feb 2013 03:46:02 +0000, trenthawkins wrote:
> Greg please ignore this if this is a stupid question, but…
>
> Is there any need to maintain the separate repo KDE Extra for Tumbleweed
> - ‘Index of /repositories/KDE:/Extra/openSUSE_Tumbleweed’
> (http://tinyurl.com/aefran8)
Only if there are packages in there that are not already in the main
tumbleweed repo. And if there are, I would ask you why that is so? You
can always ask me to include more packages in Tumbleweed, the only
requirement is that they are already in Factory, which should be the case
here, right?
> If we move to your proposed system it would be ideal if we could keep
> everything contained within the Tumbleweed repository.
Great.
> For my purposes the only reason why i have this repo enabled is because
> i use the following apps, which aren’t in the main Tumbleweed
> repository:
>
> - Dropbox (not requiring nautilus) - Is in Factory - Homerun (fullscreen
> KDE launcher) - Looks like it failed to build
> in Tumbleweed?
> - Lucky Backup - Is in Factory
If you want me to add these to Tumbleweed, just ask.
> I accept that not every app known to mankind can be in Tumbleweed,
Why not?
> but
> my understanding is that Tumbleweed includes a number of applications
> not found in the standard stable release repos? Needless to say that i
> don’t want to add to the task of maintaining Tumbleweed.
It’s a trivial thing for me to add new packages, and keep them up to date
in Tumbleweed, I have scripts that do the work for me, it’s not a manual
thing at all.
my idea would be to maybe have a opensuse tumbleweed a monthly snapshot as does linux mint with the update packs but we do not follow the update packs because I just wanted to tell you to do the opensuse tumbleweed monthly with the right patches without conflict or dependency errors. My English is not good I know, but you try to understand me if you can thanks. If we do so opensuse rolling release would be good and stable over debian testing. I would do with a new repository called tumbleweed testing or unstable how arch has stable or testing. This is just an idea of how it could simplify a little less work for you and devote more time to the bugs if possible to have a stable system and rolling without broken dependencies.
On Mon, 11 Feb 2013 20:06:03 +0000, Debiano88 wrote:
> hi Greg,
>
> my idea would be to maybe have a opensuse tumbleweed a monthly snapshot
> as does linux mint with the update packs but we do not follow the update
> packs because I just wanted to tell you to do the opensuse tumbleweed
> monthly with the right patches without conflict or dependency errors.
That’s a nice model, but sorry, that’s not what Tumbleweed is going to
do. “Snapshots” are a lot of work, much more so than I can ever do on
my own.
> My
> English is not good I know, but you try to understand me if you can
> thanks. If we do so opensuse rolling release would be good and stable
> over debian testing.
That’s what we have now, (a rolling release), and note, we aren’t trying
to “compete” with other distros here, there is no “battle” going on.
> I would do with a new repository called tumbleweed
> testing or unstable how arch has stable or testing. This is just an idea
> of how it could simplify a little less work for you and devote more time
> to the bugs if possible to have a stable system and rolling without
> broken dependencies.
I already have a openSUSE:Tumbleweed:Testing repo that I use for
“staging” big additions to the tumbleweed repos to test things out before
I push the changes out to the world. So we already have this today, if
you really want it.
On Tue, 12 Feb 2013 09:06:03 +0000, vta 128 wrote:
> I am using Lucky Backup - it would be nice to have it in TW. Thanks.
As with any package addition request, is this package in
openSUSE:Factory? If so, where should it be pulled from into Tumbleweed
(i.e. where is the “main” repo for it)?
