With great pleasure I'd would like to announce that the official release date for the Funtoo 1.0 Profiles is September 1, 2012. This is for both current and stable users. Users are encouraged to read the wiki page for instructions on switching: http://www.funtoo.org/wiki/Funtoo_1.0_Profile.
A few points to keep in mind: 1. A new version of eselect will be unmasked which supports this. Make sure you sync your tree and update eselect before trying to switch. Any one wishing to switch ahead of time just needs to unmask eselect. There's instructions in the wiki.
2. You have to manually remove the /etc/make.profile symlink in order to start using the new profiles. Until you do your system will continue to use the old profiles. This manual step is necessary to ensure that everyone's system functions correctly until they have selected their new profiles and are ready to switch.
3. Please remember to select the correct arch for your machine. Unless your using the experimental tree, there are only two options, x86-32bit (x86) and x86-64bit (amd64). Setting the wrong one could have disastrous consequences.
We will continue to support the old profiles for a little while longer after this in order to ensure all users have plenty of time to switch but eventually they will be removed.
As always, questions,, comments, issues, ect... welcomed
On Tue, Aug 14, 2012 at 1:11 PM, Ryan Harris <r...@funtoo.org> wrote:
> With great pleasure I'd would like to announce that the official release
> date for the Funtoo 1.0 Profiles is September 1, 2012. This is for both
> current and stable users. Users are encouraged to read the wiki page for
> instructions on switching: http://www.funtoo.org/wiki/Funtoo_1.0_Profile.
It's great to finally get the 1.0 profiles enabled! I think it should
be possible to have a Portage upgrade automatically take care of all
the steps for users, and this is how I would prefer to have it happen,
so it is totally seamless.
The switch supposed to be interactive and not hidden. For example, if
someone has kde installed and portage automatically switch to core profile
only (we can't hardcode all possible profile/flavor/mix-in combination)
results in unexpected updates and lots of questions. Example switch to core
profile is a 2 line (current, amd64):
> On Tue, Aug 14, 2012 at 1:11 PM, Ryan Harris <r...@funtoo.org> wrote:
> > With great pleasure I'd would like to announce that the official release
> > date for the Funtoo 1.0 Profiles is September 1, 2012. This is for both
> > current and stable users. Users are encouraged to read the wiki page for
> > instructions on switching: http://www.funtoo.org/wiki/Funtoo_1.0_Profile > .
> It's great to finally get the 1.0 profiles enabled! I think it should
> be possible to have a Portage upgrade automatically take care of all
> the steps for users, and this is how I would prefer to have it happen,
> so it is totally seamless.
On Tue, Aug 14, 2012 at 10:49 PM, Oleg Vinichenko <o...@funtoo.org> wrote:
> The switch supposed to be interactive and not hidden. For example, if
> someone has kde installed and portage automatically switch to core profile
> only (we can't hardcode all possible profile/flavor/mix-in combination)
> results in unexpected updates and lots of questions. Example switch to core
> profile is a 2 line (current, amd64):
Chatted with Ryan, we are going to make it automatic. Users can select
mix-ins when they feel like it rather than being forced. It is a
better experience.
On Wed, Aug 15, 2012 at 12:30 AM, Daniel Robbins <drobb...@funtoo.org> wrote:
> Chatted with Ryan, we are going to make it automatic. Users can select
> mix-ins when they feel like it rather than being forced. It is a
> better experience.
My current plan for this is as follows. A new portage ebuild will be
made available. This ebuild, when merged, will perform a few sanity
checks, and if things look OK, automatically switch the system over to
the 1.0 profile. If the sanity checks fail (unsupported platform,
etc.) then the user will be provided with directions on how to switch
manually.
This should be virtually seamless for virtually all standard users
running on x86 or amd64.
I hope to have a new portage ebuild masked for testing soon.
portage-2.3.4-r9 and the newest eselect will be unmasked during the next tree sync. The portage ebuild should automatically switch users to the new profiles when emerged. Please double check USE flags , ect.. after the switch and adjust accordingly. No mix-ins are enabled by default. You should also review them and add any that you might need or want.
On Wednesday, August 22, 2012 3:26:29 PM UTC-4, Daniel Robbins wrote:
> On Wed, Aug 15, 2012 at 12:30 AM, Daniel Robbins <drob...@funtoo.org<javascript:>> > wrote:
> > Chatted with Ryan, we are going to make it automatic. Users can select > > mix-ins when they feel like it rather than being forced. It is a > > better experience.
> My current plan for this is as follows. A new portage ebuild will be > made available. This ebuild, when merged, will perform a few sanity > checks, and if things look OK, automatically switch the system over to > the 1.0 profile. If the sanity checks fail (unsupported platform, > etc.) then the user will be provided with directions on how to switch > manually.
> This should be virtually seamless for virtually all standard users > running on x86 or amd64.
> I hope to have a new portage ebuild masked for testing soon.
> portage-2.3.4-r9 and the newest eselect will be unmasked during the next
> tree sync. The portage ebuild should automatically switch users to the new
> profiles when emerged. Please double check USE flags , ect.. after the
> switch and adjust accordingly. No mix-ins are enabled by default. You should
> also review them and add any that you might need or want.
In my Funtoo box the upgrade process was transparent and nice :D.
Now I have a doubt about mix-ins, where I can find a detailed
description about the objective of every mix-in?. Wiki page[0] is
great to understand the Funtoo profile improvements, but I'm not able
to find any descriptions about which is the objective of every mix-in
or the difference between workstation and workstation-minimal
> In my Funtoo box the upgrade process was transparent and nice :D.
> Now I have a doubt about mix-ins, where I can find a detailed
> description about the objective of every mix-in?. Wiki page[0] is
> great to understand the Funtoo profile improvements, but I'm not able
> to find any descriptions about which is the objective of every mix-in
> or the difference between workstation and workstation-minimal
> On Sun, Sep 16, 2012 at 4:18 PM, Víctor Orozco
> <caballerodelme...@gmail.com> wrote:
> > In my Funtoo box the upgrade process was transparent and nice :D.
> > Now I have a doubt about mix-ins, where I can find a detailed
> > description about the objective of every mix-in?. Wiki page[0] is
> > great to understand the Funtoo profile improvements, but I'm not able
> > to find any descriptions about which is the objective of every mix-in
> > or the difference between workstation and workstation-minimal
With me were suddenly / usr/portage/profiles/funtoo/1.0/linux-gnu/mix-ins/workstation-minimal and / usr/portage/profiles/funtoo/1.0/linux-gnu/mix-ins/workstation disappeared . Emerge stopped with pharse error.
So I could do something ever again, I had to create these two directories. Does anyone have any idea why this may be?
Since make.conf to /etc/portage is the program works "euse" no more, although I have seen that it has been specially adapted. It complains that the directory / directories do not exist.
/usr/bin/euse: line 105: cd :: No such file or directory /usr/bin/euse: line 103: cd: /etc/portage/make.profile / gentoo: funtoo/1.0/linux-gnu/arch/x86-64bit: No such file or directory
/etc/portage/make.profile with me a list with the parent file. There are gentoo:funtoo{path to mix-ins}.
Unfortunately, in some code is written in Python I do not understand.
remove the workstation by eselect profile remove "mix-in" (please, see the
eselect rpfile help). euse module from gentoolkit have some brokeness, that
is from upstream. Eventually, it iwll get fixed, as gentoo moved to
/etc/portage/make.conf (and profile).
On Wed, Sep 19, 2012 at 11:44 PM, Sandy Marko Knauer <
knamark...@googlemail.com> wrote:
> With me were suddenly /
> usr/portage/profiles/funtoo/1.0/linux-gnu/mix-ins/workstation-minimal and/
> usr/portage/profiles/funtoo/1.0/linux-gnu/mix-ins/workstation disappeared
> . Emerge stopped with pharse error.
> So I could do something ever again, I had to create these two directories. Does
> anyone have any idea why this may be?
> Since make.conf to /etc/portage is the program works "euse" no more, although
> I have seen that it has been specially adapted.
> It complains that the directory / directories do not exist.
> /usr/bin/euse: line 105: cd :: No such file or directory
> /usr/bin/euse: line 103: cd: /etc/portage/make.profile / gentoo:
> funtoo/1.0/linux-gnu/arch/x86-64bit: No such file or directory
> /etc/portage/make.profile with me a list with the parent file. There are
> gentoo:funtoo{path to mix-ins}.
> Unfortunately, in some code is written in Python I do not understand.
The profile workstations were not selected, it just lacked the orders. I had to create them manually and therefore I lack the make.defaults. Without this folder, I can not emerge anything.
> remove the workstation by eselect profile remove "mix-in" (please, see
> the eselect rpfile help). euse module from gentoolkit have some
> brokeness, that is from upstream. Eventually, it iwll get fixed, as
> gentoo moved to /etc/portage/make.conf (and profile).
> On Wed, Sep 19, 2012 at 11:44 PM, Sandy Marko Knauer
> <knamark...@googlemail.com <mailto:knamark...@googlemail.com>> wrote:
> With me were suddenly
> /usr/portage/profiles/funtoo/1.0/linux-gnu/mix-ins/workstation-minimaland
> /usr/portage/profiles/funtoo/1.0/linux-gnu/mix-ins/workstation
> disappeared . Emerge stopped with pharse error.
> So I could do something ever again, I had to create these two
> directories. Does anyone have any idea why this may be?
> Since make.conf to /etc/portage is the program works "euse" no more,
> although I have seen that it has been specially adapted.
> It complains that the directory / directories do not exist.
> /usr/bin/euse: line 105: cd :: No such file or directory
> /usr/bin/euse: line 103: cd: /etc/portage/make.profile /
> gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit: No such file or directory
> /etc/portage/make.profile with me a list with the parent file. There
> are gentoo:funtoo{pathto mix-ins}.
> Unfortunately, in some code is written in Python I do not understand.
knamark...@googlemail.com> wrote:
> The profile workstations were not selected, it just lacked the orders. I
> had to create them manually and therefore I lack the make.defaults. Without
> this folder, I can not emerge anything.
> Am 19.09.2012 23:06, schrieb Oleg Vinichenko:
>> remove the workstation by eselect profile remove "mix-in" (please, see
>> the eselect rpfile help). euse module from gentoolkit have some
>> brokeness, that is from upstream. Eventually, it iwll get fixed, as
>> gentoo moved to /etc/portage/make.conf (and profile).
>> On Wed, Sep 19, 2012 at 11:44 PM, Sandy Marko Knauer
>> <knamark...@googlemail.com <mailto:knamarksan@googlemail.**com<knamark...@googlemail.com>>>
>> wrote:
>> With me were suddenly
>> /usr/portage/profiles/funtoo/**1.0/linux-gnu/mix-ins/**
>> workstation-minimaland
>> /usr/portage/profiles/funtoo/**1.0/linux-gnu/mix-ins/**workstation
>> disappeared . Emerge stopped with pharse error.
>> So I could do something ever again, I had to create these two
>> directories. Does anyone have any idea why this may be?
>> Since make.conf to /etc/portage is the program works "euse" no more,
>> although I have seen that it has been specially adapted.
>> It complains that the directory / directories do not exist.
>> /usr/bin/euse: line 105: cd :: No such file or directory
>> /usr/bin/euse: line 103: cd: /etc/portage/make.profile /
>> gentoo:funtoo/1.0/linux-gnu/**arch/x86-64bit: No such file or
>> directory
>> /etc/portage/make.profile with me a list with the parent file. There
>> are gentoo:funtoo{pathto mix-ins}.
>> Unfortunately, in some code is written in Python I do not understand.
> On Thu, Sep 20, 2012 at 12:19 AM, Sandy Marko Knauer < > knama...@googlemail.com <javascript:>> wrote:
>> The profile workstations were not selected, it just lacked the orders. I >> had to create them manually and therefore I lack the make.defaults. Without >> this folder, I can not emerge anything.
>> Am 19.09.2012 23:06, schrieb Oleg Vinichenko:
>>> remove the workstation by eselect profile remove "mix-in" (please, see >>> the eselect rpfile help). euse module from gentoolkit have some >>> brokeness, that is from upstream. Eventually, it iwll get fixed, as >>> gentoo moved to /etc/portage/make.conf (and profile).
>>> On Wed, Sep 19, 2012 at 11:44 PM, Sandy Marko Knauer >>> <knama...@googlemail.com <javascript:> <mailto:knama...@googlemail.**com<javascript:>>> >>> wrote:
>>> With me were suddenly >>> /usr/portage/profiles/funtoo/**1.0/linux-gnu/mix-ins/** >>> workstation-minimaland >>> /usr/portage/profiles/funtoo/**1.0/linux-gnu/mix-ins/**workstation >>> disappeared . Emerge stopped with pharse error.
>>> So I could do something ever again, I had to create these two >>> directories. Does anyone have any idea why this may be?
>>> Since make.conf to /etc/portage is the program works "euse" no more, >>> although I have seen that it has been specially adapted. >>> It complains that the directory / directories do not exist.
>>> /usr/bin/euse: line 105: cd :: No such file or directory >>> /usr/bin/euse: line 103: cd: /etc/portage/make.profile / >>> gentoo:funtoo/1.0/linux-gnu/**arch/x86-64bit: No such file or >>> directory
>>> /etc/portage/make.profile with me a list with the parent file. There >>> are gentoo:funtoo{pathto mix-ins}.
>>> Unfortunately, in some code is written in Python I do not understand.
Ok, you shouldn't remove the parent and directories but run the above
mentioned eselect profile commands. To make things work run it again?
eselect profile clean
On Thu, Sep 20, 2012 at 12:29 AM, Sandy Marko Knauer <
knamark...@googlemail.com> wrote:
> I got this error.
> !!! Unable to parse profile: '/etc/portage/make.profile'
> !!! ParseError: Parent
> '/usr/portage/profiles/funtoo/1.0/linux-gnu/mix-ins/workstation' not found:
> '/etc/portage/make.profile/parent'
> That's why I've created these directories manually..
> Am Mittwoch, 19. September 2012 23:22:10 UTC+2 schrieb Oleg:
>> how can you cannot emerge anything?
>> On Thu, Sep 20, 2012 at 12:19 AM, Sandy Marko Knauer <
>> knama...@googlemail.com> wrote:
>>> The profile workstations were not selected, it just lacked the orders. I
>>> had to create them manually and therefore I lack the make.defaults. Without
>>> this folder, I can not emerge anything.
>>> Am 19.09.2012 23:06, schrieb Oleg Vinichenko:
>>>> remove the workstation by eselect profile remove "mix-in" (please, see
>>>> the eselect rpfile help). euse module from gentoolkit have some
>>>> brokeness, that is from upstream. Eventually, it iwll get fixed, as
>>>> gentoo moved to /etc/portage/make.conf (and profile).
>>>> On Wed, Sep 19, 2012 at 11:44 PM, Sandy Marko Knauer
>>>> <knama...@googlemail.com <mailto:knama...@googlemail.****com>> wrote:
>>>> With me were suddenly
>>>> /usr/portage/profiles/funtoo/**1**.0/linux-gnu/mix-ins/**workstati*
>>>> *on-minimaland
>>>> /usr/portage/profiles/funtoo/**1**.0/linux-gnu/mix-ins/**workstati*
>>>> *on
>>>> disappeared . Emerge stopped with pharse error.
>>>> So I could do something ever again, I had to create these two
>>>> directories. Does anyone have any idea why this may be?
>>>> Since make.conf to /etc/portage is the program works "euse" no more,
>>>> although I have seen that it has been specially adapted.
>>>> It complains that the directory / directories do not exist.
>>>> /usr/bin/euse: line 105: cd :: No such file or directory
>>>> /usr/bin/euse: line 103: cd: /etc/portage/make.profile /
>>>> gentoo:funtoo/1.0/linux-gnu/**ar**ch/x86-64bit: No such file or
>>>> directory
>>>> /etc/portage/make.profile with me a list with the parent file. There
>>>> are gentoo:funtoo{pathto mix-ins}.
>>>> Unfortunately, in some code is written in Python I do not
>>>> understand.
> Ok, you shouldn't remove the parent and directories but run the above > mentioned eselect profile commands. To make things work run it again? > eselect profile clean
