DmitryMyadzelets / inxi

Automatically exported from code.google.com/p/inxi
0 stars 0 forks source link

slackware derivatives #55

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
slitaz - i wasnt able to get inxi running as bash wasnt available, but looked 
in /etc/ for details of its version and its stored in /etc/slitaz-release. 
There were no other *release* or *version* files in the folder.

slitaz-release = cooking

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

salix - they dont have any *release* or *version* files in /etc/ other than the 
slackware-version file. so in order to detect it, you would only have to check 
for /etc/salix-update-notifier.conf and then pull the version number from 
slackware-version.

Original issue reported on code.google.com by ypha...@gmail.com on 1 Apr 2014 at 1:14

GoogleCodeExporter commented 9 years ago
/etc/slitaz-release was added to 2.1.14, i had misread your previous issue and 
missed that file was present. So that's closed.

As I noted in the 53 issue thread, I won't do custom single derived distro 
hacks in inxi distro version detection, it's already far too complex as it is.

It uses a sequence, or cascade, of distro id methods, the first is a specific 
distro file, like /etc/slitaz-release, the second is a distro file, like 
redhat-version,  the third is os-release, the last is lsb-release. Because 
there is total chaos cross distro with which method is used, ie, sometimes the 
true id is in os-release, sometimes it's in the distro specific file, some 
releases use lsb-release still as well. 

As I noted, file a bug report with salix to add the distro id file, I try to 
avoid fixing distro bugs with hacks inside inxi itself, particularly when it 
takes them only a few minutes to add that file and solve the bug.

I'm closing this issue since I believe slitaz is now handled in 2.1.14, and 
salix is a bug if no id file is included. Distros that do not wish to be id'ed 
specifically should have their wishes respected in my opinion.

By the way, in theory, the old detection should have grabbed all 
release/version files and used those automatically, but there may be cases 
where os-release is used if present. Why linux cannot think of one and only one 
method to allow for correct identification of all distros is beyond  me, 
os-release is certainly a total failure to do so, as was lsb-release.

Original comment by inxi-...@techpatterns.com on 1 Apr 2014 at 1:29

GoogleCodeExporter commented 9 years ago
i guess this can be ignored then. :)

Original comment by ypha...@gmail.com on 1 Apr 2014 at 1:31