On Monday 12 April 2010 14:29:00 Mark Knecht wrote: > On Mon, Apr 12, 2010 at 5:00 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > > Are you merely ranting or asking for help? > > > > If the former, well, OK i Hear you. But I don't care. > > > > If the latter, then you need to provide info like logs, output etc. > > > > ~amd64 works like a charm for me here. > > Neither. I think I asked a simple question. How does one get ~amd64 > @system and stable everything else? If the answer is 'you can't' or > 'it's immensely hard because you have to -~arch everything by hand' > then I'll just go back to stable, whether it is easy or requires me to > rebuild the system from scratch.
You can't do that easily, and it certainly is not advisable. The only way I can think of would be to put every package in @system into package.keywords and leave ACCEPT_KEYWORDS at arch. This will cause problems: 1. stable is just that: stable. By and large the full stable set is known to work 2. when devs commit to ~arch, they tend to run ~arch on their test boxes. Issues are easy to spot and get fixed quickly. If you have a mixture of the two, then you have a combination that no-one but you is using, and it will not have been tested. The odds are good that you will often run into problems that are hard to trace (conflicting versions of packages). Running ~arch is actually more stable than a mixture as many folk have those packages and there are more eyeballs on it. > > I'm certainly not ranting. I don't think that tone should came across > in what I wrote and if you're reading that in then it's on your end > not mine. (Although I apologize for writing anything that made that > happen!) I have __nothing__ on this system. The hardware is brand new. > It's been said time and time again that running all ~arch on other > people's systems (like yours) works great and I wanted to try it. > It's certainly not working for me at this point but I'm not upset, > mad, or anything like that. I'm asking a simple question. That's it. > Nothing more. > > I am however documenting my experiences for others than come after me > to this question of "to ~amd64 or not ~amd64". Nothing more. It worked > for Alan who is a __very__ experienced and capable person. It didn't > work for Mark (at this point) who is a 10 year Gentoo user but > __nothing__ more than a user type Those people can decide who they are > closer to in capabilities and make their choice a bit more informed. > > I didn't wake up this morning thinking I could do what you and Neil > and others on this list can with this distro. I'm not that silly! I > just wanted to try ~amd64 to see what happened. It will take me less > than 90 minutes to get to a new clean install if I blow everything > away and start over. It's not a big deal. Considering the kind of software you use, I'd advise you to just run ~amd64 and be done with it. Your usage-profile is of someone who needs recent features. I would only go back to amd64 if some genuine show-stopper blockage pops up, or if the packages you use are updated often (and usually with brand new shiny bugs - enlightenment is a lot like that which is why I had to stop using it) -- alan dot mckinnon at gmail dot com
