Thunar

[nitram]

Thunar imports great in dCore-wily but in dCore-Jessie missing icons. Tried troubleshooting and couldn't figure it out. My dCore-wily system is presently not available for comparison. Thanks.

[jls]

Hi
Wily has reached End of life, see
https://wiki.ubuntu.com/Releases

[Jason W]

There could be an icon theme in the dCore-wily setup that is missing in the dCore-jessie set of packages imported with Thunar.  I will take a look later today.

[nitram]

Previously tried believe adwaita and hi-color themes without success. Just tested and can confirm gnome-icon-theme allows dCore-Jessie's Thunar to function properly. Please add as a dependency unless you find something lighter, likewise will report back, thanks.

[Jason W]

Here is what I have found on dCore-jessie with the imports of flwm_topside, xorg-all, and thunar imported and installed.  Thunar by default on dCore-jessie imports lxde-icon-theme, and with a ~/.gtkrc-2.0 file that has the entry gtk-icon-theme-name="nuoveXT2" there are almost all icons appearing for any file types.  This costs no space.  tango-icon-theme installed and the entry gtk-icon-theme-name="Tango" shows about the same number of icons with a cost of 2MB space when tango-icon-theme and thunar are imported via a package list containing both packages.  gnome-icon-theme shows all icons even without a ~/.gtkrc-2.0 file, and is of course the full option, but adds 29MB to an sce made from a package list that contains thunar and gnome-icon-theme.

My thoughts are to use a README for Thunar that spells this out, and for those who wish to use Thunar with a small WM and not XFCE, they can refer to this. 

[nitram]

Thanks for figuring this out. On my system running xorg-intel and Fluxbox, can confirm the gtkrc file works well. The no overhead option is preferred as Thunar is already a heavy application. README sounds good, will update wiki once README posted, thanks.

jls comment about dCore-wily expiration got me thinking. From a developer standpoint would it be worthwhile to only support LTS releases to reduce workload? Just a thought, i would rather have Tiny Core and dCore around for a long time without volunteers burning out.

[Jason W]

You make a good point on including only LTS releases, I think it would reduce workload.  Though the in between releases help me with finding what changes are needed to support the next LTS release.   But with only including LTS releases, that does allow more time to determine the changes needed.  And less virtualbox and other kernel modules needed for upload, etc.  The less dCore ports to maintain, the better maintained those that exist would be. I will create a README for Thunar in the coming days.

[nitram]

FWIW my vote would be LTS only to keep the quality up, workload down. Forgot READMEs are text only, i will submit properly formatted README via PM next couple days, thanks. Also saw mention of lxappearance when troubleshooting, quite nice, autoconfigures gtkrc file and also allows changing cursor, Thunar's font size, etc.

[Onyarian]

LTS releases +1

Enviado desde mi E5803 mediante Tapatalk

[jls]

Hi
I prefer to use an up to date distro, so if Jason has got time I'd like to switch to yakkety in october. It also depends If I have time to switch.
On old release if I want up to date programs I have to use many ppas.
I don't know the process to build a dCore from ubuntu.
Jason has not provided scripts or maybe he does it manually.
For end of life ubuntu releases like wily they can be moved to an archive dir on the tinycore server.
Ciao

[Jason W]

I admit I also like to keep an up to date dCore, which can be done with Ubuntu non-LTS releases.  We can ponder it more, but I think the majority would rather focus on quality rather than quantity.  And when we take into consideration the security updates of packages and backports for a certain dCore port, that is a another set or two of packages to maintain and troubleshoot, and those package versions change as they are kept up to date.

jls - I will mail you a link to a tarball that will contain the directory of scripts and root filesystem that the dCores are made from, there is one for each dCore, I will send dCore-yakkety.  Everything is scripted, or I could not keep up with it all.  It is pretty much personal scripts of basic commands to create the dCore-*.gz image out of a rootfs directory, the commands are mentioned in the Remastering part of the wiki. 

End of life Ubuntu based dCores can be archived while their DEBINX files kept online as long as they are available from Debian/Ubuntu, for those that are older but based on actively maintained releases they can stay in the main release/RC area, ie dCore-wheezy. 

[Jason W]

README-thunar.txt from nitram now uploaded.