Rolling release distro choice
 

I have been playing around with a few rolling release distros recently (arch and lmde were the 2 that I got around to installing), but I haven't been able to find one that works for me. LMDE's packages were a bit too dated, while I found that arch updated too often (500mb of updates after a week away and a kernel update every week or so)

I was wondering if there was a distro that was somewhere between these 2, that has up to date packages, but doesn't push through updates as soon as they come out like arch does.

I have heard a bit about debian testing/unstable, but not much. would this be what I am after?

LMDE if I recall is based on Debian testing. Try Manjaro based on Arch but it's a bit slower than Arch and uses it's own repo's

LMDE is based on testing, but has its own repos, and only adds software to those repos occasionally. I was wondering if debian testing updated more often.

Took a quick look at manjaro, but am not quite convinced. It just looks like a dumbed down version of arch.

I recently switched to Gentoo on my main machine and so far it is great, I can decide which packages should go with the better tested stable branch and which packages I want to follow upstream closer with.
Needs a fair amount of time to get used to the Portage system and its enormous flexibility, but definitely worth the time, especially when you consider that you can choose which dependencies you want. I for example try to avoid Gnome/GTK wherever possible and so far there are no problems.

Been looking at gentoo a bit, but I don't think I have the time to get used to a completely new system at the moment. I'll install a few of the suggested isos on a virtualbox and play with them later. Thank God for unmetered downloads on most linux isos.

Thanks for all of the suggestions

You could run Slackware -current, or Debian sid (unstable), which in my experience is more stable than testing.

Testing is not a rolling release. Unstable is the closest thing Debian has to a rolling release, but changes there also slow down before each new Stable release. (At least from what I read.)
That is because Arch is a rolling release.
You want up-to-date, but not too up-to-date?
In other words, you want software hot off the presses, but do not want to do the work necessary to keep a rolling release functioning. If you do not want to babysit your system, it would be best to give up on the idea of a rolling release. Shiny New Shit syndrome has a strong pull, but there is a price to be paid for using a system that keeps everything shiny and new.

Might have to steal that one too

Debian Testing, and by extension LMDE, are not rolling releases. When feature freeze is enforced Testing stops updating packages and all that is done to Testing is bug fixing. Debian Sid also comes to a near standstill at this time because bug squashing is considered to be more important (and I agree with this). LMDE is also way behind the 8 ball when compared to Debian Testing unless you point the sources.list directly at Debian's, and not at Linux Mint's, repositories.

@ Tobi, I never thought you'd use anything else after moving to Slackware, but then again I didn't think you'd leave Debian either. I'll watch your experience with Gentoo with interest.

Wait Slackware veteran Tobi's using Gentoo full time? I'd love to read his experience.

Regards.

Getting back on subject, I found Arch the best - but read the news before updating to save angst.

I used Slackware for three years now, so I wouldn't call me a veteran, many members here use Slackware far longer.
Anyways. I decided to change to Gentoo for two reasons:
1. It is rolling release. Usually that wouldn't bother me, but Gentoo with the flexibility of the Portage package manager allows to easily follow upstream where it matters to me, especially the graphics stack for my Radeon video cards. Anyone who followed the threads about updating the graphics stack on Slackware sees which problem this can be on Slackware. At some point I wanted to try out if the problems I had compiling newer stuff were caused by a software regression and the easiest way to figure that out for me was to just try it with Gentoo. After spending some time with Gentoo I came to the conclusion that that is the way forward for me, it just suits my needs better than Slackware to that regard.
2. I realized that I am not opposed to automatic dependency resolution. In fact, I think no one is, not even the most die hard Slackware proponent. Simply because automatic dependency resolution doesn't exist, at some point always a human (in case of Slackware Patrick Volkerding together with his team and the good guys at Slackbuilds.org) has to figure out the dependencies and has to decide which of the optional dependencies will be compiled in (in case of Slackware also PV and his team, when it comes to SBo the user himself is at charge). The point of Slackware is not that it doesn't has automatic dependency resolution, but that the user can decide which dependencies actually should be used. Gentoo gives me the ability to decide that to a far greater extent.

Of course using Gentoo has also downsides, for example is the transition to have a fully multilib capable system still in the works. It works without a problem on a pure stable system, as well on a pure ~arch system, but not currently not without problems for a mixed system. I can for example run my Steam games, but have problems installing Wine. But this is a problem that will be fixed somewhere in the near future. Gentoo is of course also not as well tested as Slackware, but so far I had no problems regarding that. It also involves a good amount of learning, I botched three installations because I had problems to figure out how to use USE-flags and profiles properly and I will have to learn how Ebuilds work, but that is nothing that is especially hard, just time consuming.

In short, if you want a rolling release system that is well tested (as well as rolling release allows), allows you to upgrade, downgrade or halt packages at a specific version with the dependencies you want (decided on a per-package basis or in general) and you are willing to invest some time for learning, Gentoo is definitely worth a try. Any seasoned Slacker shouldn't have a problem with it, once the basic principles are understood.

Of course my journey into Gentoo is only at the beginning and it may be possible that at one point I will decide to return to Slackware, but for now I am very satisfied with Gentoo and especially the Portage package manager.

For anyone that want to figure out the different types of rolling release distros (partially rolling, fully rolling, ...) and example of distributions that use that specific release model I recommend the Wikipedia article about that topic.

Arch is the only "rolling release" distro I personally would even consider using. (But I choose not to.) The reason I say this is because Arch is designed from the ground up to be rolling release for all users; it's not like, say, Debian, a project which is primarily focused on creating a Stable release (but some people choose to run Testing/Unstable as a quasi-rolling-release anyway). Same reason I only eat sushi at sushi restaurants; I don't order sushi at Chinese restaurants that happen to also have a page of sushi at the back of their menu.

I don't know how you can say "Arch updates too often" when YOU are the one who choses when to update. If your Arch system is updating every week, it's because you are running "pacman" every week. Nobody is holding a gun to your head and forcing you to do this! If you find the updates are too frequent, then don't update so frequently.

It's also worth mentioning that Arch is one of the best distros in terms of not installing a bunch of "bloat" you don't need. The updates you're getting are only for software that YOU chose to install. Arch has a lot of "minimalist" users who run lean, mean systems with only the packages they need. The more software you chose to install, the more updates you will get, plain and simple.

I prefer Arch to any other distro, not just because of its monthly rolling release, but because of its simplicity. I had been a Gentoo user for a long time, for some of the same reasons TobySGD mentioned, but i had to move away from it because of the compile times.

If you would like to have a gentoo-ish system, without the compile times, you can check out sabayon which has grown in popularity. It is a rolling release as well, but has precompiled binaries rather than using portage.

http://www.sabayon.org/

How infrequently can the system be updated without the risk of problems? Every week? Two weeks? Every month? Not being an Arch use, but having done a fair amount of research into it, my understanding is that the longer the time between updates, the greater the chance of problems.

If you want a quick way to Arch, you could always look at Antergos, as it aims at ease-of-use like Manjaro, however it uses the Arch repos instead of its own.

Archbang's good too if you want more of a Crunchbang-style Arch install.

I know Archbang can be converted to regular Arch by changing its default configuration around, and I assume the same can be done with Antergos.

Arch is definitely the best rolling-release distro I've used. But, I haven't used Gentoo. I do have a Sabayon installation that I've been nursing along for some time now.

I feel the same way. I like running Debian Stable along with Arch; the "shiny and new," but also the "always solid and dependable."

Tobi, aren't you concerned about the wear-and-tear that Gentoo subjects your system to, due to all that compiling?

Which wear-and-tear do you mean?

The wear-and-tear caused by the massive amount of compiling that you need to do as a Gentoo user. At the very least, it's a lot of wear on the hard drive (both SSDs and rotary hard drives expire after a certain number of writes). And if you don't have good cooling, then it's also very hard on the CPU.

Wear-out of SSDs by excessive writing is a thing from the past and simply doesn't apply to modern SSDs, so I wouldn't be concerned about that if I would using the SSD for compiling, but I have configured my system to do the compiling on a tmpfs anyways, so that is a non-issue.
Regarding the CPU and cooling, I use this CPU cooler in this case (with one 200mm fan intake, one 200mm (top) and one 120mm (rear) fan outtake). This is under full load while compiling a kernel with -j7 on my Phenom II X6 1055T (125W version):Room temperature is about 20°C. The Phenom II sensors are not very accurate in that temperature range, I usually add a 10°C safety margin. CPU temperature gets about 10° higher when I overclock that machine (3.3GHz instead of 2.8GHz).

Long story short, neither wear out nor temperatures are an issue for me.

Chakra is my choice. Technically it's a semi-rolling release. I'd say it's about 600 megs a month, mostly from KDE.

Here's my sugestion.

1] Arch
2] Manjaro
3] Gentoo
4] Debian [Testing]
5] Don't use a rolling release

Folks are a few years from understanding that..

I would recommend Unstable (sid) before Testing. Ironically, unstable is generally more stable than testing.