Auto-setup ~/.config/entertainer folder

[Jamie Bennett]

** IMPORTED FROM GOOGLE CODE **
Reported by joshuascotton, Jan 13, 2008

Make this step of the installation automatic:

Under entertainer folder you can find cfg folder which is the configuration
folder of the Entertainer. Copy cfg under your home and rename it to
.entertainer (notice that dot). That's all you need to do.

Comment 1 by xiretal, Jan 13, 2008

Actually backend creates configuration folder hierarcy and default configuration
files already. The only thing that doesn't happen automatically is a theme.

Where should we install themes and how? Is /usr/share/entertainer/themes a correct
place for system wide themes?

Comment 2 by joshuascotton, Jan 13, 2008

we need the capability for local themes as well as system wide
/usr/share/etertainer/themes would be as good a place as any for system wide themes

Comment 3 by xiretal, Jan 13, 2008

Sure, user can install themes under ~/.entertainer/themes. This can be done using
preferences gui. So it's very easy. But when Entertainer is installed we should
install default theme system wide, so that frontend can always fallback to that if
nothing else can be found.

Comment 4 by joshuascotton, Jan 15, 2008

(No comment was entered for this change.)

Owner: ---
Comment 5 by rockstar.dev, Feb 06, 2008

I'm rather reluctant to have Entertainer install files in system paths during this
early stage of development. When we get to a beta stage and things get a little more
permanent, then we can start installing system-wide files. Until then, let's install
the default them in the $HOME/.entertainer folder somewhere.

Comment 6 by laymansterms.dev, Mar 12, 2008

I agree with rockstar, we shouldn't install stuff in system paths at this time. I'll
spawn a new issue to make sure we don't lose the theme placement issue, but it is
secondary to this issue.

Issue 3 was fixed with Rev 320.

Status: Fixed
Owner: laymansterms.dev
Labels: Component-Persistence
Comment 7 by rockstar.dev, Mar 13, 2008

This bug is still not completed, however. The problem with rev 320 is that, since
we're working in our our private space, the current patch works fine. However, what
happens when the skeleton configs are stored in /usr/share/entertainer/config of
something similar.

I don't want to close this bug until we all come to a conclusion on how it will work.
 Obviously, each distros packages will ship with a patch specific to their
installation anyway, but we need a good solution that works outside of a standard dev
environment.

[Matt Layman (mblayman)]

Migrating the importance over from Google Code.

[Matt Layman (mblayman)]

Jamie has laid the groundwork for this by moving all the information into the configuration dir variable in the configuration object. Now I think we just need a check in the configuration object to see if the directory exists, and if not, create it by copying the cfg directory (some of that code maybe already be in the source in the frontend from earlier work that I did, but it's in the wrong place).

[Matt Layman (mblayman)]

Since I don't think the email just for merge proposals is working yet, I've attached my comment about a failing test here. Input from any of the devs for handling this problem would be appreciated.

Merge proposal comment:
The test functions properly when run from the src level. I'm not sure how to resolve this so that it will run at the tests directory level because the create_cfg_dir uses an absolute path in order to find the cfg directory. Any suggestions on how to make this work from either level would be appreciated (I'm not sure how I could find the cfg directory without an absolute path that is determined relative to the src directory).

[Matt Layman (mblayman)]

Released and available at http://www.entertainer-project.com/download.php