A semi-incomplete X-mas wish list - and some more things :)

--===============5013911353972100949==
Content-Type: multipart/alternative; boundary="94eb2c188716a71e940560177f3d"

--94eb2c188716a71e940560177f3d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello GoboFolks,

This is just a short email really. :)

First, happy x-mas and new year holidays!

Since I mentioned x-mas, I wanted to write a longer mail about
x-mas wishes for GoboLinux, but that mail became too long; more
than 300 lines. I think it's hard to write and read long mails.

At any rate, just a few points of note:

- I noticed lucas announcement about AlienVFS
https://github.com/gobolinux/AlienVFS
He also improved the docu a while ago. :)

I'll give it a try eventually, primarily on slackware, but I am
a very slow snail. Sometimes I do more stuff, sometimes less.
But sooner or later I often get around to do something more
useful than watching cat videos on youtube. Or drunk squirrels,
damn ... I should consider banning youtube since I spend too
much time there. Anyway.

- One of my projects in ruby is the cookbooks gem. I tried to
make the documentation better... current variant is at:

  http://www.rubydoc.info/gems/cookbooks/0.0.1107

It's far from perfect but bear with me. I'll improve it
eventually. It now also comes with an (autogenerated)
listing of programs, program versions and program URLs.

http://www.rubydoc.info/gems/cookbooks/0.0.1107#Available_program_versions

Now this has nothing to do with GoboLinux but ... I
recently FINALLY finished adding all the major programs
for KDE. There are about +400 programs or so listed there
related to KDE5 (including plasma, kde applications such
as konsole, and KDE5 KF frameworks). I also tested the
scripts that can automatically download KDE5 software
when a new update is pushed by the KDE devs, and so far
these scripts work fine. That means that I can now, quite
easily, keep up to date with the KDE team. Perhaps we
can have a way to have KDE5 work on GoboLinux too - I am
too much of a noob to figure out everything with cmake,
but I managed to compile most of KDE5 up to (and including)
KDE konsole on slackware a few months ago. And it actually
worked.

So that's one wish list entry for xmas, perhaps next year
for GoboLinux, to have KDE work on GoboLinux. I can also
autogenerate some pages - I uploaded a test of this at
http://shevegen.square7.ch/programs.html

Something isn't quite right there for me when I view it
with firefox; it works with opera. Anyway, I'll improve
this at some later time. The thing is that I wanted to
list all the descriptions, homepage settings etc... so
that it can be made easier to also generate GoboLinux
recipes.

- SLAX is back! \o/

Anyone remembers SLAX? The cool thing about SLAX was that
you could easily build your own customized distribution.
You just added modules; it somehow worked with aufs.

I think this should be doable with GoboLinux too, perhaps
even already-is with the scripts. Just a bit hard to know
how ... I haven't tried myself.

Only bad news is that SLAX is no longer based on slackware
but went into debian and thus systemd (ugh) - but the author
explained why. It was not because of systemd, but it was
because debian made it a lot easier for him to just do
"apt-get install NAME", rather than recompile stuff all
the time. I understand this. GoboLinux also has a small
base installation by default these days. :)

I remember the KDE3 days! We had oldschool KDE konsole
too... damn has KDE become more complex and complicated.

(I was not able to compile KDE5 before, by the way, always
some problem with qt + kde ... and cmake too, boy...)

My xmas wish list here for the new year is to also be
able to have SLAX on GoboLinux, but with the GoboLinux
file system layout. Then I could perhaps make a customized
.iso variant that includes KDE (if I can get KDE to work
on GoboLinux ... there is one problem related to docbook*
which I don't know how to resolve on EITHER slackware OR
GoboLinux ... but docbook is needed for some things, also
on gnome, for dconf ...)

Here a link to the SLAX blog: http://www.slax.org/nn/blog.php

- Anyway, I did not want to write too much so I will soon
finish.

Some time ago, I mentioned that I think that the GoboLinux
recipe situation is not ideal, altogether. It's too complicated
IMO, it is also quite slow. The manual approval thing is ok,
it ensures quality but ... do we really need to have all
recipes reviewed manually? Is a description or licence or
homepage entry really needed?

There also may be some bug or so ...

http://recipes.gobolinux.org/r/ has not been updated in +60
days but there were new recipes at github, which confuses
me a bit.

I also think that the recipes way that gobolinux currently
uses, will not work for e. g. KDE with its +400 programs.

Someone may have to manually go through each of these AND
get them to work, too. And that is cumbersome, takes a
lot of time, too.

Now let's assume that the KDE5 team manages to make everything
work fine via cmake. Then we, on GoboLinux, should be
easily able to get things to work as well, right? On
slackware, the kde-stuff and cmake loves to install things
into /usr/lib/cmake/. Not sure how this is done on GoboLinux
but perhaps even a hardcoded directory entry at /usr/lib/cmake/
may work. I have no idea.

What I am trying to say or suggest is ... perhaps we can use
another layer of recipes? Some that are much simpler.

For example, ultimately we only need a single file with
the URLs to the remote stuff.

https://download.kde.org/unstable/applications/17.11.90/src/konsole-17.11.9=
0.tar.xz
https://download.kde.org/unstable/applications/17.11.90/src/spectacle-17.11=
.90.tar.xz
https://download.kde.org/stable/frameworks/5.41/attica-5.41.0.tar.xz

And so forth.

Ideally, this list would be autogenerated, in the right
compile-order (first listed is the one to be first
compiled).

Then, when such a list exists, we could compile this on
GoboLinux, and hopefully, it would all work.

Am I getting through with this to anyone? :)

In the above, a script could just automatically determine
the name of the program at hand. One of my ruby projects
does this, called program_information -

https://rubygems.org/gems/program_information

From the commandline, I can do e. g.:

  pinfo
https://download.kde.org/unstable/applications/17.11.90/src/konsole-17.11.9=
0.tar.xz

ProgramInformation: Program real short name    (@real_short_name) is:
`konsole`
ProgramInformation: Program name               (@short_name     ) is:
`konsole`
ProgramInformation: Program version            (@program_version) is:
`17.11.90`

It works fairly well, but of course one could do the same in python,
lua or shell code. Some programs are a bit more difficult to handle;
I am using a few regexes to determine which is the real program
name and which is the real program version.

Anyway. The above would make it fairly simple to install KDE on
GoboLinux right? Provided that everything compiles fine.

We could also use a hybrid system, such as using such a file,
but if the GoboStore (did I just coin this word) has a recipe
available, it could be automatically updated too.

Anyway, I am not sure if I am able to explain what I want to explain.

I think I would like to have some easier way to have larger stacks
such as KDE work on GoboLinux too. Recipes could be generated
automatically too. GoboLinux could fill in the dependencies etc...
and dump such "test" recipes. We already have code that helps
with generating recipes, so that should no be a big problem.

I can also autogenerate such a list by the way, via the cookbooks
gem (changing the code in the cookbooks gem is trivial for me).

I could also do this for gnome. The script could also check whether
something has already been compiled successfully before, and skip
when things have been compiled successfully.

So for example, in the simplest form, if we have KDE Konsole
available from:


https://download.kde.org/unstable/applications/17.11.90/src/konsole-17.11.9=
0.tar.xz

We can check on the directory

  /Programs/Konsole/17.11.90/

And if this directory exists, we could naively assume that the program
is installed. This may not always be the case, but I am trying to keep
things simple here.

That way, people could just compile the KDE stack from a "meta" recipe
or instruction, but without necessarily depending on GoboLinux recipes
per se.

Anyway, I finish here because I have no way if that makes any sense
to anyone else at all. :)

Happy holidays to everyone! I do not know how the weather is in
brazil at this time of the year, but it's getting quite cold in
central europe; night yesterday was at ~1=C2=B0C and it is projected
to get colder towards new year eve.

--94eb2c188716a71e940560177f3d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello GoboFolks,<br><br>This is just a short email really.=
 :)<br><br>First, happy x-mas and new year holidays!<br><br>Since I mention=
ed x-mas, I wanted to write a longer mail about<br>x-mas wishes for GoboLin=
ux, but that mail became too long; more<br>than 300 lines. I think it&#39;s=
 hard to write and read long mails.<br><br>At any rate, just a few points o=
f note:<br><br>- I noticed lucas announcement about AlienVFS <a href=3D"htt=
ps://github.com/gobolinux/AlienVFS">https://github.com/gobolinux/AlienVFS</=
a><br>He also improved the docu a while ago. :)<br><br>I&#39;ll give it a t=
ry eventually, primarily on slackware, but I am<br>a very slow snail. Somet=
imes I do more stuff, sometimes less.<br>But sooner or later I often get ar=
ound to do something more <br>useful than watching cat videos on youtube. O=
r drunk squirrels,<br>damn ... I should consider banning youtube since I sp=
end too<br>much time there. Anyway.<br><br>- One of my projects in ruby is =
the cookbooks gem. I tried to <br>make the documentation better... current =
variant is at:<br><br>=C2=A0 <a href=3D"http://www.rubydoc.info/gems/cookbo=
oks/0.0.1107">http://www.rubydoc.info/gems/cookbooks/0.0.1107</a><br><br>It=
&#39;s far from perfect but bear with me. I&#39;ll improve it <br>eventuall=
y. It now also comes with an (autogenerated)<br>listing of programs, progra=
m versions and program URLs.<br><br><a href=3D"http://www.rubydoc.info/gems=
/cookbooks/0.0.1107#Available_program_versions">http://www.rubydoc.info/gem=
s/cookbooks/0.0.1107#Available_program_versions</a><br><br>Now this has not=
hing to do with GoboLinux but ... I <br>recently FINALLY finished adding al=
l the major programs<br>for KDE. There are about +400 programs or so listed=
 there<br>related to KDE5 (including plasma, kde applications such<br>as ko=
nsole, and KDE5 KF frameworks). I also tested the <br>scripts that can auto=
matically download KDE5 software <br>when a new update is pushed by the KDE=
 devs, and so far<br>these scripts work fine. That means that I can now, qu=
ite<br>easily, keep up to date with the KDE team. Perhaps we <br>can have a=
 way to have KDE5 work on GoboLinux too - I am<br>too much of a noob to fig=
ure out everything with cmake, <br>but I managed to compile most of KDE5 up=
 to (and including)<br>KDE konsole on slackware a few months ago. And it ac=
tually<br>worked.<br><br>So that&#39;s one wish list entry for xmas, perhap=
s next year<br>for GoboLinux, to have KDE work on GoboLinux. I can also<br>=
autogenerate some pages - I uploaded a test of this at<br><a href=3D"http:/=
/shevegen.square7.ch/programs.html">http://shevegen.square7.ch/programs.htm=
l</a><br><br>Something isn&#39;t quite right there for me when I view it<br=
>with firefox; it works with opera. Anyway, I&#39;ll improve<br>this at som=
e later time. The thing is that I wanted to<br>list all the descriptions, h=
omepage settings etc... so<br>that it can be made easier to also generate G=
oboLinux<br>recipes.<br><br>- SLAX is back! \o/<br><br>Anyone remembers SLA=
X? The cool thing about SLAX was that<br>you could easily build your own cu=
stomized distribution.<br>You just added modules; it somehow worked with au=
fs.<br><br>I think this should be doable with GoboLinux too, perhaps<br>eve=
n already-is with the scripts. Just a bit hard to know<br>how ... I haven&#=
39;t tried myself.<br><br>Only bad news is that SLAX is no longer based on =
slackware<br>but went into debian and thus systemd (ugh) - but the author<b=
r>explained why. It was not because of systemd, but it was<br>because debia=
n made it a lot easier for him to just do<br>&quot;apt-get install NAME&quo=
t;, rather than recompile stuff all<br>the time. I understand this. GoboLin=
ux also has a small<br>base installation by default these days. :)<br><br>I=
 remember the KDE3 days! We had oldschool KDE konsole<br>too... damn has KD=
E become more complex and complicated.<br><br>(I was not able to compile KD=
E5 before, by the way, always<br>some problem with qt + kde ... and cmake t=
oo, boy...)<br><br>My xmas wish list here for the new year is to also be<br=
>able to have SLAX on GoboLinux, but with the GoboLinux<br>file system layo=
ut. Then I could perhaps make a customized<br>.iso variant that includes KD=
E (if I can get KDE to work<br>on GoboLinux ... there is one problem relate=
d to docbook*<br>which I don&#39;t know how to resolve on EITHER slackware =
OR<br>GoboLinux ... but docbook is needed for some things, also<br>on gnome=
, for dconf ...)<br><br>Here a link to the SLAX blog: <a href=3D"http://www=
.slax.org/nn/blog.php">http://www.slax.org/nn/blog.php</a><br><br>- Anyway,=
 I did not want to write too much so I will soon<br>finish.<br><br>Some tim=
e ago, I mentioned that I think that the GoboLinux<br>recipe situation is n=
ot ideal, altogether. It&#39;s too complicated<br>IMO, it is also quite slo=
w. The manual approval thing is ok,<br>it ensures quality but ... do we rea=
lly need to have all<br>recipes reviewed manually? Is a description or lice=
nce or<br>homepage entry really needed?<br><br>There also may be some bug o=
r so ...<br><br><a href=3D"http://recipes.gobolinux.org/r/">http://recipes.=
gobolinux.org/r/</a> has not been updated in +60 <br>days but there were ne=
w recipes at github, which confuses<br>me a bit.<br><br>I also think that t=
he recipes way that gobolinux currently<br>uses, will not work for e. g. KD=
E with its +400 programs.<br><br>Someone may have to manually go through ea=
ch of these AND<br>get them to work, too. And that is cumbersome, takes a<b=
r>lot of time, too.<br><br>Now let&#39;s assume that the KDE5 team manages =
to make everything<br>work fine via cmake. Then we, on GoboLinux, should be=
 <br>easily able to get things to work as well, right? On<br>slackware, the=
 kde-stuff and cmake loves to install things<br>into /usr/lib/cmake/. Not s=
ure how this is done on GoboLinux<br>but perhaps even a hardcoded directory=
 entry at /usr/lib/cmake/<br>may work. I have no idea.<br><br>What I am try=
ing to say or suggest is ... perhaps we can use<br>another layer of recipes=
? Some that are much simpler.<br><br>For example, ultimately we only need a=
 single file with<br>the URLs to the remote stuff.<br><br><a href=3D"https:=
//download.kde.org/unstable/applications/17.11.90/src/konsole-17.11.90.tar.=
xz">https://download.kde.org/unstable/applications/17.11.90/src/konsole-17.=
11.90.tar.xz</a><br><a href=3D"https://download.kde.org/unstable/applicatio=
ns/17.11.90/src/spectacle-17.11.90.tar.xz">https://download.kde.org/unstabl=
e/applications/17.11.90/src/spectacle-17.11.90.tar.xz</a><br><a href=3D"htt=
ps://download.kde.org/stable/frameworks/5.41/attica-5.41.0.tar.xz">https://=
download.kde.org/stable/frameworks/5.41/attica-5.41.0.tar.xz</a><br><br>And=
 so forth.<br><br>Ideally, this list would be autogenerated, in the right<b=
r>compile-order (first listed is the one to be first<br>compiled).<br><br>T=
hen, when such a list exists, we could compile this on<br>GoboLinux, and ho=
pefully, it would all work.<br><br>Am I getting through with this to anyone=
? :)<br><br>In the above, a script could just automatically determine<br>th=
e name of the program at hand. One of my ruby projects<br>does this, called=
 program_information - <br><br><a href=3D"https://rubygems.org/gems/program=
_information">https://rubygems.org/gems/program_information</a><br><br>From=
 the commandline, I can do e. g.:<br><br>=C2=A0 pinfo <a href=3D"https://do=
wnload.kde.org/unstable/applications/17.11.90/src/konsole-17.11.90.tar.xz">=
https://download.kde.org/unstable/applications/17.11.90/src/konsole-17.11.9=
0.tar.xz</a><br><br>ProgramInformation: Program real short name=C2=A0=C2=A0=
=C2=A0 (@real_short_name) is: `konsole`<br>ProgramInformation: Program name=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 (@short_name=C2=A0=C2=A0=C2=A0=C2=A0 ) is: `konsole`<br>ProgramIn=
formation: Program version=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 (@program_version) is: `17.11.90`<br><br>It works fairly=
 well, but of course one could do the same in python,<br>lua or shell code.=
 Some programs are a bit more difficult to handle;<br>I am using a few rege=
xes to determine which is the real program<br>name and which is the real pr=
ogram version.<br><br>Anyway. The above would make it fairly simple to inst=
all KDE on<br>GoboLinux right? Provided that everything compiles fine.<br><=
br>We could also use a hybrid system, such as using such a file,<br>but if =
the GoboStore (did I just coin this word) has a recipe<br>available, it cou=
ld be automatically updated too.<br><br>Anyway, I am not sure if I am able =
to explain what I want to explain.<br><br>I think I would like to have some=
 easier way to have larger stacks<br>such as KDE work on GoboLinux too. Rec=
ipes could be generated <br>automatically too. GoboLinux could fill in the =
dependencies etc...<br>and dump such &quot;test&quot; recipes. We already h=
ave code that helps<br>with generating recipes, so that should no be a big =
problem.<br><br>I can also autogenerate such a list by the way, via the coo=
kbooks<br>gem (changing the code in the cookbooks gem is trivial for me).<b=
r><br>I could also do this for gnome. The script could also check whether<b=
r>something has already been compiled successfully before, and skip<br>when=
 things have been compiled successfully.<br><br>So for example, in the simp=
lest form, if we have KDE Konsole<br>available from:<br><br>=C2=A0 <a href=
=3D"https://download.kde.org/unstable/applications/17.11.90/src/konsole-17.=
11.90.tar.xz">https://download.kde.org/unstable/applications/17.11.90/src/k=
onsole-17.11.90.tar.xz</a><br><br>We can check on the directory<br><br>=C2=
=A0 /Programs/Konsole/17.11.90/<br><br>And if this directory exists, we cou=
ld naively assume that the program<br>is installed. This may not always be =
the case, but I am trying to keep<br>things simple here.<br><br>That way, p=
eople could just compile the KDE stack from a &quot;meta&quot; recipe<br>or=
 instruction, but without necessarily depending on GoboLinux recipes<br>per=
 se.<br><br>Anyway, I finish here because I have no way if that makes any s=
ense<br>to anyone else at all. :)<br><br>Happy holidays to everyone! I do n=
ot know how the weather is in <br>brazil at this time of the year, but it&#=
39;s getting quite cold in <br>central europe; night yesterday was at ~1=C2=
=B0C and it is projected<br>to get colder towards new year eve.<br></div>

--94eb2c188716a71e940560177f3d--

--===============5013911353972100949==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZ29ib2xpbnV4
LXVzZXJzIG1haWxpbmcgbGlzdApnb2JvbGludXgtdXNlcnNAbGlzdHMuZ29ib2xpbnV4Lm9yZwpo
dHRwOi8vbGlzdHMuZ29ib2xpbnV4Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dvYm9saW51eC11c2Vy
cwo=

--===============5013911353972100949==--