Spritz Package Manager 0.3 and 3.5 Loop2
A first yet basic (but cool) release of Spritz is going to hit our repository in the next hours. I’ve made some screenies you can watch below. Yeah, this is another milestone in the process of creating THE next-gen package manager 
. Other than this, 3.5 Loop2 will be released before the 10th of March 2008. Featuring a LOT of bug fixes, features, and so forth.
Categories: Development
3.5 loop 1 works amazingly well for me, there’s no rush for loop 2
Sabayon Linux keeps getting better & better, keep-up the fantastic work Fabio & the Dev’s of course!
that looks absolutely gorgeous! really looking forward to 3.5 … the package management until that was much too complicated for me… mainly because I didn’t had the time to look into it.. but this looks >>really<< promising!
just one last word: KISS (keep it simple, stupid) ^^
Could you please consider for Loop2 not use PAE kernel for x86, or add a non-PAE kernel as a boot option? VirtualBox does not support PAE which is very unfortunate, as livedvd won’t even boot.
Will the 2.6.24.2 kernel be used? I ask because some major security hole was fixed in that version that has existed since 2.6.17. Also, KDE 3.5.9 is in Portage, will that be updated as well? And what about Firefox?
all that is already in Entropy.
Fabio will you do something for speeding up the boot time? SuSE used to be extremely in boot time and now it boots to KDM in 20 seconds. Before it needed around 45-50. I believe you can speed it up if you want as well.
Something more. Fabio please try to create a REALLY stable version of Sabayon as other distros do. Bleeding edge Linux hightech can be on the Sabayon-dev for example. Sabayon stable should be built on a Gentoo profile which sacrifices bleeding edge to stability. I am really frustrated of emerge commands which fail to compile e.t.c. Please allow us to have a Sabayon distro where everything should work out of the BOX including Suspend in RAM, Sound, Nvidia, Compiz e.t.c.
i wish i could donate some money before i can ask something. good job everyone!
@ashley194
With my new PC, all Sabayon versions including Loop1 are useless. I cross my fingers and hope with each new release that I can actually use it. So its not good enough for all of us. Loop2 I am eager to see you.
thedevilsjester, new hardware is far beyond software always. This is how it works. Brand new laptops with new drivers and new ACPI do not come with Linux Drivers unfortunately. Only Windows Drivers. All of us should buy laptops or try to buy laptops which are designed for Linux and not Microsoft Windows or VISTA. However those are not yet that popular. The problem here with Sabayon, is something more. They have this Professional Edition, which is supposed to be stable, but it has been built on a profile which is not thoroughly tested and also has a lot of problems with Wireless ACPI and other stuff. What I suggested to lxnay above and I apologize if nobody understood me (my manners are not that good I am sorry about that) is to make sure that there will always be a Professional or Stable Edition which will be 100% Stable. Please sacrifice bleeding edge for Stability. After all, what do we need bleeding edge if it is full of bugs and nothing works. I would rather – and I believe that many people agree with me – a version which will definitely work with no problems at all and I could spare a partition on my hard-drive for the bleeding edge stuff for testing and feedback reporting. lxnay we are not against you buddy, we are with you, but it is better to slow down a little bit and look more seriously on the Stable branch.
More news will come about Professional. Other than that, Sabayon is stable. if you have a kernel problem, it’s not due to our fault. Same thing with AMD/ATI drivers. Sorry.
I have NVIDIA drivers not AMD/ATI. I know that you are pretty stable all I am suggesting is that you should be more concerned about stability than bleeding edge. As for the drivers I have ipw3945 and PE 1.1 cannot connect from KNetworkManager (yeah yeah I know I have re-emerged ipw3945 driver and daemon e.t.c.) while Elive and Ubuntu and SuSE connect nicely and easily. This looks like a Sabayon problem. Look we are not accusing you here. Nor we are underestimating your efforts. But all Sabayon people say without a second thought we are pretty stable and give more efforts to bleeding edge stuff and not stability and robustness of their product. All I am saying I will say it again: Turn your Attention towards Stability.
Don’t use PE. Get a 3.5 Loop2 when it’ll be out and read all the install methods the installer gives you. “Core” is my favourite
ipw3945 has always worked fine on 3.4 and 3.5, I own one, while Luca doesn’t.
anyway, OTOH, you’re absolutely right. I’ll make 3.5 become what Professional should have always been.
I am waiting with my fingers crossed lxnay. Core is nice. I used it for benchmarking code. code runs faster there and also more memory if free. No X no daemons running. An environment for scientific code benchmarking. OTOH I am with you man. I wish I could join the team and do some developing for you. I have no time though not at all. It is awful. I have so many ideas about making portage much faster (implementing a cache for (emerge -s, emerge -pv) system ) Sabayon much more reliable, find a great window manager and create a Sabayon light edition with a very light WM which can also provide composite stuff and will be really eye-candy. Benchmark with scientific codes several kernel parameters and provide a Sabayon deployment for scientific computing. I wish I could help you guys. Everything I say it is not for blaming or something just to give directions from which we will all benefit.
@archwndas
Yeah, except that other distros, even a year old, work with my new PC fine, so you cannot blame “new technology”.
thedevilsjester low down man. Nobody pays those people they are not professionals. They are just young guys below 30 who are working hard for free. Sabayon is a brand new Distros compared with the others out there. Being so young though it has the greatest development rate from any other Distro I have ever tried. I mean that features and programs e.t.c. are added in a much faster pace than anywhere else. The only problem they have is that they are not patient. They should have given more attention to a stable branch of Sabayon than they did. I believe though they have realized that. Another issue is their Forum. Too many sub-categories. Hard to maintain. There should be only 4 or 5:
Stable x86
Stable AMD64
Development x86
Development AMD64
Bugs
Inside each post the guy who submit it could tick something like:
Network related
File System related
Portage Related
ACPI related
e.t.c.
and then the post would be forwarded to the inbox of the corresponding maintainer. This way we would have much more immediate feedback and it would be also much easier for them to maintain and fix bugs e.t.c.
They are quite young though and they have much to learn. What encourages me to continue using this Distro is 2 things:
A) Gentoo Portage
B) Their hard work which results to a fast progress rate.
In about one year you will not believe in your eyes what those people would have accomplished. They should though borrow ideas from other distros like ww.elivecd.org.
@archwndas
You are reading more into my posts then I am putting. I havent complained, nor have I begged them to fix it, or whine about it not working.
I said that I would really like to use Sabayon again, but I cannot with the current releases, so I eagerly look forward to Loop2 in hopes that my issue has been resolved.
Loop1 == BETA. That hard to understand?
@lxnay
If you are referring to me, no version of Sabayon works, beta or otherwise. I am well aware that Loops are betas, you do not have to take that tone with me. I look forward to the next Loop only because change could very well mean a fix to my problem.
If you are referring to someone else, well then, carry on sir.
never tried to properly report your issues, thedevilsjester?
@Ixnay
Just like you are by no means required to fix anything for us, neither am I required to report issues.
I am not demanding that you fix it, I am not asking that you fix it, I am not whining or complaining about it not working. I am simply crossing my fingers and hoping the next build will be the one that works. As was suggested to me on the forums.
In case you are curious
http://www.sabayonlinux.org/forum/viewtopic.php?f=52&t=12837
I don’t see any log attacched. How can I fix it then?
@lxnay
First: I have never asked you to fix it.
Second: The forum post I requested help in, no one came and asked for a log. I have hundreds of logs on my PC, should I post every one of them? Is there a specific log you would need? How am I supposed to give a log, when I havent the slightest idea whats wrong?
As far as I know, the bug has been fixed already even in stable versions. However since I cannot connect to the web I have no (reasonable) way of updating to the latest fixes to find out.
This is where Loop2 comes in. As a snapshot of the current state of Sabayon (even a beta), if the issue has been resolved, then I will know it. If not, then I can see about having it traced, reported, and fixed.
It does me little good to report a bug that for all I know may already be fixed.
If, however, you still want logs, tell me (in the forum post) which logs you want, and I would be happy to provide them.
Calm down or I’ll remove your posts.
@lxnay
?
You are reading way more into my posts then I put.
All I said was that I eagerly await Loop2 because Loop1 and earlier do not work for me. Somehow that got turned into a “oh he is complaining” argument.
I am not asking you to fix a bug that I do not if it still exists.
The first thing thats suggested when you have a bug is to update to the newest versions to see if that bug has been fixed yet, before posting reports.
Since I cannot access the web through Sabayon, I am waiting for Loop2 so I have updated packages. That is all. I am not yelling, I am not mad, I am patient.