EndeavourOS apps info: where does it come from?

Since a few days back I have discovered an application called EndeavourOs apps info in my system. I’m pretty (?) sure that I had never seen it before. Is it a new addition to eos-shared-bash? Otherwise I cannot explain how I could have missed it all along.

pacman -Ql eos-bash-shared
eos-bash-shared /etc/
eos-bash-shared /etc/eos-apps-info/
eos-bash-shared /etc/eos-apps-info/eos-apps-info.conf
eos-bash-shared /etc/eos-apps-info/pageinfo/
eos-bash-shared /etc/eos-apps-info/pageinfo/ChangeDisplayResolution.url
eos-bash-shared /etc/eos-apps-info/pageinfo/RunInTerminal.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/UpdateInTerminal.url
eos-bash-shared /etc/eos-apps-info/pageinfo/akm.url
eos-bash-shared /etc/eos-apps-info/pageinfo/bashdb.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/checkupdatesext.url
eos-bash-shared /etc/eos-apps-info/pageinfo/device-info.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/downgrade.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-apps-info.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-bash-shared.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-connection-checker.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-download-wallpapers.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-hooks.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-log-tool.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-pacdiff.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-pkg-changelog.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-pkginfo.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-rankmirrors.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-sendlog.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-shifttime.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-update-notifier-configure.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-update-notifier.url
eos-bash-shared /etc/eos-apps-info/pageinfo/eos-wallpaper-set.url
eos-bash-shared /etc/eos-apps-info/pageinfo/grub-colour-chooser.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/grub-tools.url
eos-bash-shared /etc/eos-apps-info/pageinfo/inxi.helpcmd.foo
eos-bash-shared /etc/eos-apps-info/pageinfo/inxi.url
eos-bash-shared /etc/eos-apps-info/pageinfo/mirrorlist-rank-info.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/nvidia-installer-check.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/nvidia-installer-db.url
eos-bash-shared /etc/eos-apps-info/pageinfo/nvidia-installer-dkms.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/paccache-service-manager.url
eos-bash-shared /etc/eos-apps-info/pageinfo/pahis.url
eos-bash-shared /etc/eos-apps-info/pageinfo/polybar.url
eos-bash-shared /etc/eos-apps-info/pageinfo/rate-mirrors.helpcmd.foo
eos-bash-shared /etc/eos-apps-info/pageinfo/rate-mirrors.url
eos-bash-shared /etc/eos-apps-info/pageinfo/reflector-bash-completion.url
eos-bash-shared /etc/eos-apps-info/pageinfo/reflector-simple.url
eos-bash-shared /etc/eos-apps-info/pageinfo/su-c_wrapper.url
eos-bash-shared /etc/eos-apps-info/pageinfo/virtualbox.url
eos-bash-shared /etc/eos-apps-info/pageinfo/vscode.url
eos-bash-shared /etc/eos-apps-info/pageinfo/wallpaper-dnd.url
eos-bash-shared /etc/eos-apps-info/pageinfo/wallpaper-once.url
eos-bash-shared /etc/eos-apps-info/pageinfo/welcome.url
eos-bash-shared /etc/eos-apps-info/pageinfo/yad-eos.url
eos-bash-shared /etc/eos-apps-info/pageinfo/yad-icon-browser.helpcmd
eos-bash-shared /etc/eos-apps-info/pageinfo/yay.helpcmd.foo
eos-bash-shared /etc/eos-apps-info/pageinfo/yay.url
eos-bash-shared /etc/eos-script-lib-yad.conf
eos-bash-shared /etc/eos-sendlog.conf
eos-bash-shared /usr/
eos-bash-shared /usr/bin/
eos-bash-shared /usr/bin/ChangeDisplayResolution
eos-bash-shared /usr/bin/RunInTerminal
eos-bash-shared /usr/bin/RunInTerminalEx
eos-bash-shared /usr/bin/RunInTerminalOpt
eos-bash-shared /usr/bin/UpdateInTerminal
eos-bash-shared /usr/bin/device-info
eos-bash-shared /usr/bin/eos-FindAppIcon
eos-bash-shared /usr/bin/eos-apps-info
eos-bash-shared /usr/bin/eos-apps-info-helper
eos-bash-shared /usr/bin/eos-connection-checker
eos-bash-shared /usr/bin/eos-download-wallpapers
eos-bash-shared /usr/bin/eos-kbd-set
eos-bash-shared /usr/bin/eos-pacdiff
eos-bash-shared /usr/bin/eos-pkg-changelog
eos-bash-shared /usr/bin/eos-pkginfo
eos-bash-shared /usr/bin/eos-pkginfo-aur
eos-bash-shared /usr/bin/eos-run-cmd-with-su
eos-bash-shared /usr/bin/eos-sendlog
eos-bash-shared /usr/bin/eos-shifttime
eos-bash-shared /usr/bin/eos-waiting-indicator
eos-bash-shared /usr/bin/eos-wallpaper-set
eos-bash-shared /usr/bin/grub-colour-chooser
eos-bash-shared /usr/bin/paccache-service-manager
eos-bash-shared /usr/bin/su-c_wrapper
eos-bash-shared /usr/share/
eos-bash-shared /usr/share/applications/
eos-bash-shared /usr/share/applications/UpdateInTerminal.desktop
eos-bash-shared /usr/share/applications/eos-apps-info.desktop
eos-bash-shared /usr/share/bash-completion/
eos-bash-shared /usr/share/bash-completion/completions/
eos-bash-shared /usr/share/bash-completion/completions/eos-pkginfo
eos-bash-shared /usr/share/endeavouros/
eos-bash-shared /usr/share/endeavouros/scripts/
eos-bash-shared /usr/share/endeavouros/scripts/eos-script-lib-yad
eos-bash-shared /usr/share/endeavouros/scripts/ksetwallpaper.py

3 Likes

:shushing_face:


2 Likes

Ahh…secret project!?
:dark_sunglasses:

1 Like

:thinking: Is the new release nearly coming? :rocket:

6 Likes

:speaking_head: I told you not to tell anyone! :man_facepalming:

1 Like

You mean this?
image

1 Like

More like this:
appinfo

Oops! Appearances are NOT everything :grin: Sure a variety of different info presentations though!

:beers:

@pebcak @s4ndm4n @freebird54
Just use it, but as said by others, don’t tell anyone yet! :wink:
And please report problems… :innocent:

4 Likes

will do.

Is this leading to a need for Wiki entries for each - so that it can be called up this way? Or - some alternate form of man-like pages that can be called up?

Or - is this to prevent that from being needed! :grin:

Speaking as a Wiki contributor, of course… :duck:

1 Like

To be honest, I don’t know yet.
There are pros and cons in all alternatives.
It would be nice to have a uniform set of info pages, but it takes quite much time to achieve that.
So if anyone can help with the design and implementation, that would be very much appreciated. :sweat_smile:

1 Like

My first thought is to implement wiki entries for most of them, by entering/expanding(?) the Git readme.md where possible. My second thought is to create an eos-man (?) which displays the readme.md files more directly, without needing a browser. Either way, some judicious editing is probably the way to go - perhaps a mini-tutorial on usage?

Obviously you haven’t the time for that - you’re creating/maintaining them! I guess I should go digging and see what I can come up with for a few of them for you to see what it would look like…

I’ll get a start on that pretty quick - it sounds (strange, I know) fun in a quirky way.

3 Likes

How about having info on our wiki website?

I’ll be available to write wiki pages (if needed) throughout September.

man pages is another option, but I wonder how many users actually read that… Man pages can work offline, in case that’s necessary.

3 Likes

The information about EndeavourOS packages is in many different places now.
For offline info pages, if a decent md viewer is available, then we could use that.

We already have quite many md documentation files. In addition we have wiki pages. These two formats are the largest amount of information. Other formats are a minority currently, so they could be converted to a better format, either md or wiki (which are not far apart from each other). Note that we have man pages and command help pages as well…

But feel free to examine this and let me know what you think! Maybe you come up with the best solution! :sweat_smile:

2 Likes

If this is to be the information center for EnOS tools then I would like to propose using MD or man pages for offline use. Because if we go with the WiKi then users need to have an active internet connection. Keeping these smaller information files offline would be good in case of no internet access.

I’m not a big-time programmer but I have taught myself some C# (I should have gone with C++ or C), PHP, JavaScript, and a few other web tech stuff (mainly backend not a front end person). But work as an IT admin (servers and network stuff). I can help with WiKi pages or any other documentation if needed. You guys have seen my blog (minus the spelling issues :smiley:).

Or any other way if the project leads ask of me.

3 Likes

I tend to agree with your thoughts on that, with the exception that I think the information should be on the wiki as well. Whether the default is to go with the offline version, or perhaps check if online and then decide - that is for later. Things are better presented online for clarity, however - because trying to make the offline look good might well require some additional packages. Even something simple like mdless (md version of less, with additional navigation) pulls in a bunch of ruby stuff to function… and something like lynx I haven’t even tried yet! Maybe I’ll have to dust off my ‘C’ skills to make something better. Anyone got a powerful leaf blower handy? :grin:

Actual ‘C’? Yup - C++ and C# etc didn’t exist back then… I used ‘C’ where it didn’t seem worth it to write in 680x0 assembly! I miss the Amiga…

1 Like

This was my first thought but didn’t say it because it’s still in its baby stage. A better mechanism should be to check if an active connection is there if there is set the wiki as info DB if not set offline pages. But to get this off the ground we should try to keep it simple. I do agree with you.

I started with TC and TP (Turbo Pascal). Then I lost touch because my profession targeted the networking side. But I still try my best to learn to program because I love to stare at walls and to pull my hair out searching for a missing semi-colon.

1 Like

Hmmm - Turbo Pascal… I remember that, although I tended to use Modula-2 more - then Delphi - but I tried a lot of things!

Anyway - What is needed is a consistent look for markdown, then I can import/transfer them to the Wiki easily enough. Offline, the mdless works OK, but I wish I had fewer dependencies involved. More research needed - but Markdown is still a good thing to have done. Here’s a pic of some sample .md file in mdless for reference:
mdless

Usable, but not thrilling! Another possibility is converting .md to .html and feeding it to lynx - but let’s get them all in 1 place/style first!

2 Likes

If you need my help with anything I’m here.

1 Like