You are not logged in.
Pages: 1
Hello!
When will a new version of ArchLinux be released? Thanks1
Offline
When it is ready...
Edit: Noticed you are new here. In case you don't know, the actual releases mean very little compared to other distros because Arch uses a rolling release system.
Last edited by Allan (2008-02-16 13:29:28)
Offline
I'm sorry. What does that mean?
Offline
Offline
Have you read the wiki? http://wiki.archlinux.org
rolling release means that u always are updating your system when updates 'roll' in... There is no set date of a release, if an new version of a program is released upstream then arch dev's will package that new release that day or soon and have it available for d/l so u can update your system. Since not everyone works on the same schedule, this means your updates come whenever they feel like it, so the release is considered 'rolling' over a period of time.
This is why arch is considered 'bleeding edge' you are always up to date.
edit: allen beat me by one minute
Last edited by jacko (2008-02-16 14:15:41)
Offline
Yes, this isn't ubuntu, were all the packages are updated ever 6th month.
Use the Source, Luke!
Offline
Anyone who's gone too many times through the "Wow, new realease ... ack, nothing works right" cycle can appreciate the rolling release philosophy. You can still have problems with package upgrades, but these are easier to deal with because your system on the whole is otherwise solid.
noobus in perpetuus
Offline
Anyone who's gone too many times through the "Wow, new realease ... ack, nothing works right" cycle can appreciate the rolling release philosophy. You can still have problems with package upgrades, but these are easier to deal with because your system on the whole is otherwise solid.
That's one thing that I disliked back in my days as an Ubuntu user. New versions were provided every 6 months and the upgrades were not always smooth. There was usually a couple threads on the forum devoted exclusively to bugs for those who performed the upgrade. Rolling release is bliss. ![]()
- "Cryptographically secure linear feedback based shift registers" -- a phrase that'll get any party started.
- My AUR packages.
- I use i3 on my i7.
Offline
Anyone who's gone too many times through the "Wow, new realease ... ack, nothing works right" cycle can appreciate the rolling release philosophy. You can still have problems with package upgrades, but these are easier to deal with because your system on the whole is otherwise solid.
Very true. However, a rolling release distro means that you need to get down and dirty when the problems arise since you may be the only user to experience it if you use an uncommon package.
Last edited by mintcoffee (2008-02-18 04:41:59)
Arch on a Thinkpad T400s
Offline
Wasn't it rumored that when 2.6.24 kernel comes out we will have brand new shiny iso? ![]()
Offline
I guess that this, too, will just be ready when it is ready. But yes, the larger logic behind would require an iso with 2.6.24.
Offline
Please, a new starting iso will be great ![]()
Even if 2007.08-2 is usable, a younger one will be a blessing ![]()
Offline
I think Arch will release with every new Kernel a new release. It will be great if there will be also a new Install CD's. 2007.11 is done with out a Install CD's. How about 2008, is there something on the way?
openSUSE
Arch Linux
USALUG
Offline
To be honest, i'd also like the facility to roll-back upgrades, this is the major downside to the rolling-release system that arch uses. If a package breaks your system then you have no ability to switch back to the version you had previously installed unless you keep the packages cached. Which is not always an option if you are running on limited space.
The problem with the repositories at the moment is that they ONLY have the most up to date packages available. Granted this isn't a problem for most people, but it could be a life-saver under certain circumstances.
Offline
To be honest, i'd also like the facility to roll-back upgrades, this is the major downside to the rolling-release system that arch uses. If a package breaks your system then you have no ability to switch back to the version you had previously installed unless you keep the packages cached. Which is not always an option if you are running on limited space.
The problem with the repositories at the moment is that they ONLY have the most up to date packages available. Granted this isn't a problem for most people, but it could be a life-saver under certain circumstances.
read the wiki, there is a server that actually has old outdated packages specifically for downgrading. If not, then it tells you how u can build your own outdated package. Its really not that hard!
http://wiki.archlinux.org/index.php/Downgrade_packages
Last edited by jacko (2008-02-19 21:45:45)
Offline
SiC, I believe the option to downgrade packages through the official pacman application has plans to be in some upcoming release in the future. Jacko was accurate in directing you to the noted wiki page, which details a couple possible solutions to your problem. If you are tight on space, the CVS entries on the server will allow you to build packages with "makepkg" from years ago. I would not imagine this would be too much of a problem, as I would expect that most up-to-date, Arch packages will work on your system without the need to compile older versions unless, of course, you simply do not like to compile with makepkg.
I also do not know how the ability to roll back packages will be included in a future pacman or any other extending application. One possible way the feature could be implemented is that on an issued command to downgrade a package, pacman would first check the /var/cache/pacman/pkg directory to see if the indicated package is present. If it does not exist, then pacman may compile an older version for you with the CVS entries saved on Arch's server in a temporary directory and, afterwords, install the requested package. The first step of checking /var/cache/pacman/pkg will probably not be too valuable in your situation, I suppose, but the second step I think may be. But the second step is simply what you get from running the "makepkg" command inside an arbitrary directory with the proper PKGBUILD and included files, and obtaining a PKGBUILD for the desired version of the application is not a problem since all the old versions of them are on the CVS server. And if you are up to it, I don't think designing an application to automate this process is necessarily out of the question; it could save some valuable time in the long run.
Without error there can be no brilliancy. ― Emanuel Lasker
Offline
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/
the abs makpkg build system is now one of my favorite features of arch. With this system its easy to go back to any release date of a package and get the files u need to rebuild that package in any state. Complete flexibility and it so simple its almost stupid.
KISS
Offline
I think Arch will release with every new Kernel a new release. It will be great if there will be also a new Install CD's. 2007.11 is done with out a Install CD's. How about 2008, is there something on the way?
Sure, many nice things are coming, just be patient. ![]()
to live is to die
Offline
Pages: 1