1 |
The problem I have with using Sabayon to ultimately install Gentoo is it |
2 |
takes way too much work than just doing a Gentoo install... |
3 |
|
4 |
You would have to uninstall all entropy applications and begin using |
5 |
just portage, edit make.conf (look for sabayon mirrors), rebuild world, |
6 |
replace Sabayon Kernel with Gentoo kernel, change framebuffer splash |
7 |
from Sabayon, remove overlay and rebuild all over again, and then hunt |
8 |
down the rest of the Sabayon-specific files. You will have breakage. |
9 |
That doesn't even take into account downgrading from ~amd64. If you are |
10 |
doing that much rebuilding, it's faster just to do it yourself |
11 |
originally. |
12 |
|
13 |
---- |
14 |
J. Rutkowski |
15 |
|
16 |
On Tue, Jul 21, 2015, at 07:26 AM, Andrew Savchenko wrote: |
17 |
> On Tue, 21 Jul 2015 08:34:00 +0000 (UTC) Duncan wrote: |
18 |
> > Andrew Savchenko posted on Tue, 21 Jul 2015 03:05:04 +0300 as excerpted: |
19 |
> > |
20 |
> > > occasionally I need a tool to "fast install Gentoo and fine-tune it |
21 |
> > > later". This happens quite often on a new job box, |
22 |
> > > oh during visits where I'm given a workstation and 3-4 hours to set it |
23 |
> > > up before doing real work and so on. |
24 |
> > > |
25 |
> > > The idea is to have binary-based Gentoo ready to work on general common |
26 |
> > > hardware with such software out of the box as fully-fledged modern gui |
27 |
> > > browsers (chromium, firefox), libreoffice, xterm, screen, vim, |
28 |
> > > compilers, ldap support and other dev tools. Set of packages may vary, |
29 |
> > > but the idea is that they should work out of the box due to tight |
30 |
> > > constrains on initial system configuration (boss should see that I'm |
31 |
> > > doing my job at the end of the day). |
32 |
> > > |
33 |
> > > But afterwards I'd like to tune this setup in a usual Gentoo way: |
34 |
> > > configure kernel, USE flags, {C,CXX,F,FC,LD}FLAGS, select proper |
35 |
> > > alternatives and so on more or less accordant to the devmanual. |
36 |
> > |
37 |
> > I've never used it myself, but from what I've read, that's pretty much |
38 |
> > what the gentoo-based sabayon linux does. It's a binary-based distro |
39 |
> > that lists as a major feature (from its homepage): |
40 |
> > |
41 |
> > >>> |
42 |
> > |
43 |
> > Binary vs Source Package Manager |
44 |
> > |
45 |
> > It's up to you whether turn a newly Sabayon installation into a geeky |
46 |
> > Gentoo ~arch system or just camp on the lazy side and enjoy the power of |
47 |
> > our binary, dumbed down Applications Manager (a.k.a. Rigo). With Sabayon |
48 |
> > you are really in control of your system the way you really want. |
49 |
> > |
50 |
> > <<< |
51 |
> > |
52 |
> > [After reading a bit on the sabayon site to satisfy my own curiosity as |
53 |
> > well, something I had been meaning to do anyway...] |
54 |
> > |
55 |
> > When first installed, sabayon has a portage config synced with the sabayon |
56 |
> > build servers, same USE, etc. The recommendation is to choose either |
57 |
> > entropy, the native sabayon binary package manager, or portage, and stick |
58 |
> > with it, but there's documentation available for "advanced users" who |
59 |
> > want to keep the two in sync and thus be able to use both, or who want to |
60 |
> > switch (presumably from sabayon prebuilt binaries to gentoo build-from- |
61 |
> > source) later. Do note that sabayon is based on gentoo/~amd64, however, |
62 |
> > so switching to stable amd64 will be downgrading. Also, they use the |
63 |
> > hard-masked-in-gentoo portage-9999 live-build version, so even switching |
64 |
> > to ~amd64 portage will be a (generally minor) downgrade for it. |
65 |
> > |
66 |
> > So a quick sabayon install and update via entropy, followed by an update |
67 |
> > of the portage config (the entropy package updates will have diverged |
68 |
> > from the initially synced state) using the appropriate tool, should leave |
69 |
> > you with a generally current and synced system built from binaries. |
70 |
> > |
71 |
> > That's your working system at end-of-day. |
72 |
> > |
73 |
> > At that point you can switch to portage using the instructions provided, |
74 |
> > review and change any USE flags and other portage settings you wish, and |
75 |
> > do an emerge --newuse --update --deep @system and @world, and the result |
76 |
> > should be basically the same as if you'd done it the conventional gentoo |
77 |
> > way. The biggest caveat is likely to be if you were targeting stable |
78 |
> > amd64, not ~amd64, since that'd be a downgrade, since sabayon is ~amd64 |
79 |
> > based. But it should be as possible as it is on gentoo, since that's |
80 |
> > essentially what you're left with after the switch to portage, a gentoo |
81 |
> > ~amd64 system. |
82 |
> > |
83 |
> > |
84 |
> > FWIW, this is the big reason I've never been a big booster of either a |
85 |
> > gentoo GUI installer (automating things for mass installation using a |
86 |
> > script is an entirely different thing, tho), or a gentoo binpkg project. |
87 |
> > Gentoo is good at what it does, the stage-3, initial manual install, and |
88 |
> > from-source ebuild scripts and the main tree, and gentoo-based distros |
89 |
> > already provide good binary and GUI-install solutions. As such, gentoo |
90 |
> > itself trying to do either gui installs or binpkg primary packaging is |
91 |
> > going to be coming late to the game and reinventing wheels other gentoo- |
92 |
> > based distros have not only already invented, but are already quite |
93 |
> > expert in. Let each one keep to its strengths and the whole ecosystem |
94 |
> > will be better for it. =:^) |
95 |
> > |
96 |
> > And while sabayon is apparently currently ~amd64 only, given their |
97 |
> > experience doing a gentoo-based binary distro, I'd suggest that it'd be |
98 |
> > far more efficient to join sabayon and get a build going that targets |
99 |
> > gentoo stable or whatever alternative arch instead of ~amd64, than it |
100 |
> > would be to try to do a full-fledged gentoo-binpkg alternative project. |
101 |
> > Again, let each build on its strengths and together build a bigger and |
102 |
> > stronger community, as a result. =:^) |
103 |
> > |
104 |
> > But like I said, I _do_ believe there's a place for an automated build- |
105 |
> > script install solution operating from a pre-made configuration file, to |
106 |
> > automate the mass-install end of things. To my knowledge, there's no |
107 |
> > existing gentoo-based distro doing that, yet, so it's a hole waiting to |
108 |
> > be filled. =:^) |
109 |
> |
110 |
> Thank you for the information. I never investigated possibility to |
111 |
> use Gentoo derivatives (aside from system rescue cd) for such task |
112 |
> because I was not sure if they allow switching to pure Gentoo |
113 |
> system afterwards. |
114 |
> |
115 |
> Looks like Sabayon is a good solution for such cases, so I'll test |
116 |
> it on next occasion. |
117 |
> |
118 |
> Best regards, |
119 |
> Andrew Savchenko |
120 |
> Email had 1 attachment: |
121 |
> + Attachment2 |
122 |
> 1k (application/pgp-signature) |