Request guix for TC9 x86

[flavien]

Hello!
It would be great to get TCZs (for TC9 x86) :

• lirc*
• lcdproc*
• guix

*(should contains kernel files)

Maybe help for Guix : https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html#Binary-Installation

I'm a new TC user (just since some days ago), so i'm not sure to produce good TCZ files now.
Sorry for my poor english speaking.

[flavien]

Oops. "One thread for extension".
Sorry!
This thread is for guix

[Juanito]

Isn't guix an os/package management system?

[flavien]

Yes, but in user space.
It does not depend of any distribution.
It's like snapd, but as a real package manager, with shared libraries (but multi versions)
Theorically, i can, for example, get full kodi-18-rc with all dependencies installed in the persistant context in 1 or 2 lines in terminal. 

[flavien]

I will try to make it this month if nobody do it before, because it could be easy with available binaries releases

[coreplayer2]

Yes, but in user space.

As is APPS

Theorically, i can, for example, get full kodi-18-rc with all dependencies installed in the persistent context in 1 or 2 lines in terminal. 

Like APPS

Seems as if you haven't discovered APPS yet?

[flavien]

Never heard about, but not sure it's the same.
Is this "OpenCollaborationServices" ?
If no, what's the difference?
If yes, APPS/OCS seems to be an abstract package management layer, but not a package manager.
It does't install anything, but command the distribution to do it. Right?

Guix is a real package manager, but to install packages and dependencies in user space without writing files out of /home...

[coreplayer2]

Flavien,   APPS is the Official GUI version of TinyCore extension management, find it on the wbar

From the command-line

Code: [Select]

tce-ab
tce-load
tce-audit

[coreplayer2]

Flavien,  I think you'd be smart to read the Core Book.  http://tinycorelinux.net/book.html

[flavien]

I just forgot the TCE GUI name, as it's just a TCE frontend.
But sure I understand the TCE advantages, that's why i begin to use Tiny Core...
So APPS, alias TCE, can but does not install programs in user space (i mean like '/home'), but in rootfs (usualy in "/" root ramfs). But yes persistence allows keeping programs in user space (by squashfs or backup). Of course.

Guix is "same", but different.
To run GUIX on any distribution, you just have to install the daemon and run it.

I think TCE is perfect to deploy light packages and can offer various elegants "over mounts" strategies.
But for an as big as kodi program, it could be very hard to maintain (various architectures, run dependencies, build dependencies, compilation...)

GUIX packages theorically offer an absolute portability on any distributions.
So imagine you get your light tiny core environemment (like a swiss knife), and over it, you can deploy up to date big packages by using GUIX, then you don't have to maintain millions of TCE packages, as it's for light usage.


Last point:
You decide to update the GUIX part only? It will not affect tiny core.
You decide to update the tiny core part only? It will not affect GUIX installation.
You have two versions of tiny core using a same real home path?
Your GUIX programs could be available on each!

[coreplayer2]

I just forgot the TCE GUI name, as it's just a TCE frontend.
But sure I understand the TCE advantages,

No sorry but at present I don’t think you do..

I think TCE is perfect to deploy light packages and can offer various elegants "over mounts" strategies.
But for an as big as kodi program, it could be very hard to maintain (various architectures, run dependencies, build dependencies, compilation...)

Maybe you missed that KODI  is already in the repo..  it’s not that large.

GUIX packages theorically offer an absolute portability on any distributions.
So imagine you get your light tiny core environemment (like a swiss knife), and over it, you can deploy up to date big packages by using GUIX, then you don't have to maintain millions of TCE packages, as it's for light usage.

Last point:
You decide to update the GUIX part only? It will not affect tiny core.
You decide to update the tiny core part only? It will not affect GUIX installation.
You have two versions of tiny core using a same real home path?
Your GUIX programs could be available on each!

I hear what you’re selling, but I’m not buying it.. If the book didn’t make it clear I recommend you study the Core Concepts
http://tinycorelinux.net/concepts.html

Then imagine the Tinycore way [emoji2]



Sent from my iPhone using Tapatalk

[Pats]

Quote from: flavien on Today at 12:10:42 PM :
 ... But for an as big as kodi program, it could be very hard to maintain (various architectures, run dependencies, build dependencies, compilation...)

I have not used kodi in TC before and dont know  exact defination of *big programs* .

.. But prvs TCE  packages  like  JDK , Xine, Apache, Oracle,  MySQL , GIMP, LibreOffice , GNOME , Opera,   etc  may  not be big enough as per recent *big* or *heavy-weight* defination ! 

[coreplayer2]

So, I have a 3D game which is around 10GiB in size which I think qualifies a large.    I believe this game is far too large for a Home directory which requires routine backups, is currently stored on a separate partition and communicates with 3D kernel mode drivers when run. 

Additionally I run a 3D test program which is approximately 300MiB in size and it has no difficulty being installed from a tc extension archive.

I just can't see how either program would benefit from being adapted to to run from Guix..

[mocore]

I will try to make it this month if nobody do it before, because it could be easy with available binaries releases

i did try running the install for the binaries release , and i think it was working after some modification to the script ( wrt user creation ..the program names differ in TC afair , and installing some dependent programs )

i might have the notes some place , and nix and guix are on my ever-growing to do list

 tc methods has some advantages over them ( at least nix i have not much used guix), to note a few 0)simplicity ,1) tcz.list of package file's aka provides.db

but also to be fair nix/guix are not "just" a package manager but also a build system ...
( shout out to The ubiquitous lemur of doom! Muhahaha!!! and  associated from SCRATCH topic )


.. a build system ... much like some others that can be found in the "Programming & Scripting - Unofficial" section

eg : tc-ext-tools buildscripts , tce-make , and friends

the one advantage imho that nix/guix bring is larger / growing community creating / updating the packages 

...also in theory it should be possible to create a tcz package using nix/guix

[flavien]

When I say big, i mean big/hard/or long to build and maintain. (Sorry for my poor english.)

@mocore : I totaly agree!

..the program names differ in TC afair , and installing some dependent programs

I'm not 100% sure, but theorically guix does not care about.
All is in /gnu/store + /usr/guix + /home/$USER and/or /root folders.
So you should (in theory) never get a clonflict!
When you build for NIX/GUIX, you potentialy build for all linux distributions (+ maybe for the non linux gnu hurd os).

...also in theory it should be possible to create a tcz package using nix/guix

Excelent !

Taking advantage of building guix system, then create tcz packages!
In GUIX isolation terms : /gnu/store and a lot of symlinks, not classic simple linux organisation, of course.
But why not?! 

And even if you don't use GUIX to make TCZ, when a package is not now available in TCZ repo (like kodi 18-rc vs kodi 17), you can install and test the RC version from GUIX and wait for stable kodi 18 before trying to eventually get it in a beautiful TCZ light package! (less frequency work needed in making releases for TC contributors to get a full usable and flexible OS!) Isn't great ?!

After dCore, Guix Core ?