Background image install paths.

johnraff · 2016-04-11 02:05:44

damo wrote:

Hmmm, complicated

Yes, unfortunately.

1) A BLOB first-run warning about older saved lightdm settings.

Of course we have no way of knowing what might have happened to the lightdm files between installation and running BLOB. The user should have an idea though, so maybe a warning would be enough.

2) Remove the lightdm option completely.

And any other system-level tweaks. As a last resort, this would be the simplest way out perhaps.

3) Don't try to save/restore lightdm config, but have a message to the user to re-run alternatives.

Would work. There are other GUI tweaks available in lightdm-gtk-greeter.conf though, like the theme, which users might want to alter anyway.

4) Automate the edit of alternatives. Possible?

Yes. It's quite possible to add/remove alternative choices and set one as the Alternative, all from a script.

5) Another possibility that ocurred to me is that BLOB could come with a built-in set of configs, stored as "default", that corresponds to the initial install, so when first starting BLOB, "default" would already come up as an available stored session.
Would a ~/.config/blob/default directory be enough, or would ~/.config/blob/current need to be set to "default" too? Would it work without a default.jpg image? Or could that just be made something generic-looking? Since BLOB comes in bunsen-utilities, not bunsen-configs (which installs skel) then perhaps bunsen-utilities could put BLOB's "default" stuff in /usr/share and copy it into ~/.config/blob on BLOB's first run?

----------------------

BTW filenames: would it be OK if I just rename things as I see fit, or would you like to handle it? Also, can you post a revised README somewhere? I don't think it needs much adding to it, just tidying out the obsolete lines.

It would be good to get the "newpaths" packages built and on the repo so @hhh can get the new CD iso out. Maybe this BLOB issue can be fixed after that - it will only affect a few users at this point I guess.

damo · 2016-04-11 06:37:55

johnraff wrote:

...
5) Another possibility that ocurred to me is that BLOB could come with a built-in set of configs, stored as "default", that corresponds to the initial install, so when first starting BLOB, "default" would already come up as an available stored session.
Would a ~/.config/blob/default directory be enough, or would ~/.config/blob/current need to be set to "default" too? Would it work without a default.jpg image? Or could that just be made something generic-looking? Since BLOB comes in bunsen-utilities, not bunsen-configs (which installs skel) then perhaps bunsen-utilities could put BLOB's "default" stuff in /usr/share and copy it into ~/.config/blob on BLOB's first run?

This has come up before, in reference to shipping some different configs. I like the idea of including the BL default config though. Could it just be included in skel and installed during the user setup? A "generic" scrot should work - like the one on the BL homepage.

BTW filenames: would it be OK if I just rename things as I see fit, or would you like to handle it? Also, can you post a revised README somewhere? I don't think it needs much adding to it, just tidying out the obsolete lines.
......

I'll let you deal with the paths, and I'll have a look at the README later.
-------
EDIT: I don't see anything "obsolete" in README.blobthemes?

Last edited by damo (2016-04-11 20:02:10)

johnraff · 2016-04-12 06:29:48

damo wrote:

I like the idea of including the BL default config though. Could it just be included in skel and installed during the user setup?

Skel seems like the way to go. Since BLOB already knows how to make a set of backup configs by looking in $HOME, maybe the (almost) same code could make a "Default" session backup by going over /usr/share/bunsen/skel? The (very cool ) screenshots bit would have to be skipped I guess. If that Default session backup was made on BLOB's first run, rather than at user setup time, it would save a user who never touched BLOB from having an unnecessary ~/.config/blob directory. Also, if the backup was based on the current skel/ it would save us having to keep two sets of configs in sync.

BTW filenames: would it be OK if I just rename things as I see fit, or would you like to handle it? Also, can you post a revised README somewhere? I don't think it needs much adding to it, just tidying out the obsolete lines.
......
I'll let you deal with the paths, and I'll have a look at the README later.
-------
EDIT: I don't see anything "obsolete" in README.blobthemes?

I didn't mean BLOB's README, I meant the bunsen-images README here: https://github.com/BunsenLabs/bunsen-im … ths/README

#61 2016-04-11 02:05:44

Re: Background image install paths.

#62 2016-04-11 06:37:55

Re: Background image install paths.

#63 2016-04-12 06:29:48

Re: Background image install paths.

Board footer