Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
Sent with Proton Mail secure email. On Sunday, June 1st, 2025 at 6:44 PM, David Lecompte wrote: > > Isn't ungoogled-chromium already available from Trisquel repositories? I > > installed it from there on Trisquel 12. > > > Yes, I noticed but this is new in Trisquel 12, it isn't in Trisquel 11. For how long would Trisquel 12 be for testing? > -- > David Lecompte [email protected] > > ___ > Trisquel-devel mailing list > [email protected] > https://listas.trisquel.info/mailman/listinfo/trisquel-devel ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
> Isn't ungoogled-chromium already available from Trisquel repositories? I > installed it from there on Trisquel 12. > Yes, I noticed but this is new in Trisquel 12, it isn't in Trisquel 11. -- David Lecompte ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
Hello David, Isn't ungoogled-chromium already available from Trisquel repositories? I installed it from there on Trisquel 12. Best regards, Xavi On 30 May 2025 12:28:12 CEST, David Lecompte wrote: >> > One suggestion could be to use the Guix package manager available at >> > Trisquel. >> >> I shall look into the capability very closely. >> > >On every non-headless Trisquel machine I install for myself or someone else, >I install guix. One reason is to have ungoogled-chromium, as it happens that >a few important websites are not functional enough with abrowser. > >I follow exactly the procedure in the Trisquel wiki for this (there is a >link to it from the "All manuals" page), on Trisquel with MATE environement. >I have used guix once succesfully with KDE on wayland but I recall that some >extra things were needed as KDE did not use /etc/profile.d/guix.sh installed >by the guix package. I should try this again and add to the wiki the extra >configuration needed. > >Two things to note: >- there have been slow response from savannah when running "guix pull", >often getting a 504 error in response. In this case, retrying until it works >can be a solution. However, there is a mirror (which may become or already >have become the main repository, but I did not follow the discussions) on >codeberg which was much faster recently. To use it, add "-- >url=https://codeberg.org/guix/guixhttps://codeberg.org/guix/guix"; after >"guix pull". >- when running "guix install package_xxx" or "guix upgrade", if there are no >substitutes (pre-built binaries) available for some needed packages, your >computer will try building them. If this is ungoogled-chromium, on my >machines, it typically takes several days, if it ever succeeds at all. If >that happens, I just do Control+C to interrupt it and wait a few days before >retrying. It is possible to only upgrade specific packages by running "guix >upgrade package-xxx package-yyy". > >Have a good time with Guix on Trisquel ! > >However, if you use Parabola, you very quickly have the most up-to-date >version of packages. I regularly travel with a computer with Parabola as >only distro installed, it is fine as a daily driver. > >In my opinion, the main drawbacks of Parabola are that: >- Parabola installation is not automatic, you need to do basic configuration >according to the wiki and think of installing all the packages you need >(like the right xorg driver, that I tend to forget), it took me a bit of >time to get it working for the first time, but then it is fine as a daily >driver. You could try it with a virtual maching in Trisquel. To make your >life a little easier, use the systemd option, at least until you get >familiar enough with Parabola. >- It regularly happens that system upgrade (which one should normally do >before installing any package) is not possible, often because some package >in the "libre" repository (from Parabola) needs to be rebuilt due to some >package upgrade in archlinux repositories (used by Parabola). Any failure of >system upgrade should be reported so that Parabola developers are aware and >fix it. Check the issues marked "sticky" and if any matches with your >problem, add a comment to it, otherwise check "recent issues" and if none >matches with your problem, create a bug report. > >-- >David Lecompte >___ >Trisquel-devel mailing list >[email protected] >https://listas.trisquel.info/mailman/listinfo/trisquel-devel ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
Sent with Proton Mail secure email. On Saturday, May 31st, 2025 at 7:54 PM, David Lecompte wrote: > > The following package will be installed: > > emacs-next 28.0.50-0.2ea3466 > > > I had not checked before, the latest version in Guix is 29.4, while Parabola > has 30.1-5. For software available both in Guix and in Parabola, I have seen > such a situation several times: Guix has much more recent version than > Trisquel, but not as recent as Parabola. > > What does "guix describe" say? For me, it is > > Generation 1 May 17 2025 16:57:07 (current) > guix 9f3d8db > repository URL: https://codeberg.org/guix/guix-mirror > branch: master > commit: 9f3d8dbda60bb1dd15d2956c334354947df8b3f5 > > > So I have relatively recent version (17 May 2025). > > If doing your development work in a virtual machine is feasible, you could > create a virutal machine with Parabola. I don't do any development, but on > my laptop (with i5-1240P), it is feasible to put the display of a virtual > machine full screen and use it as the main computer for all my tasks. > -- > David Lecompte [email protected] Have finally managed to get GNU Emacs 30.0.92 with Guix Package Manager on top of Trisquel from the help here. ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
> The following package will be installed: > emacs-next 28.0.50-0.2ea3466 > I had not checked before, the latest version in Guix is 29.4, while Parabola has 30.1-5. For software available both in Guix and in Parabola, I have seen such a situation several times: Guix has much more recent version than Trisquel, but not as recent as Parabola. What does "guix describe" say? For me, it is Generation 1May 17 2025 16:57:07(current) guix 9f3d8db repository URL: https://codeberg.org/guix/guix-mirror branch: master commit: 9f3d8dbda60bb1dd15d2956c334354947df8b3f5 > So I have relatively recent version (17 May 2025). If doing your development work in a virtual machine is feasible, you could create a virutal machine with Parabola. I don't do any development, but on my laptop (with i5-1240P), it is feasible to put the display of a virtual machine full screen and use it as the main computer for all my tasks. -- David Lecompte ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
On Saturday, May 31st, 2025 at 3:04 AM, David Lecompte wrote: > Le vendredi 30 mai 2025 à 16:58 +0200, David Lecompte a écrit : > > > > Have run 'guix install emacs' which installed 'emacs 27.2'. > > > > > > Finally guix gave the hint below > > > > > > hint: Consider setting the necessary environment variables by running: > > > > > > GUIX_PROFILE="/home/hagbard/.guix-profile" > > > . "$GUIX_PROFILE/etc/profile" > > > > > > How would the hint be implemented in my .bashrc file? > > > > > > Like so: > > > > > > GUIX_PROFILE="/home/hagbard/.guix-profile" > > > > > > ## > > > ## source "$GUIX_PROFILE/etc/profile" # or the command K2 > > > . "$GUIX_PROFILE/etc/profile" # K2 > > > > If you use Trisquel with MATE, all the necessary variables are set at > > login, > > there is no need to follow these advices. So you can simply log out and > > log > > in and they will be set properly, or you can run "bash -l" as advised in > > the > > wiki (-l stands for login, so that files in /etc/profile.d are sourced, > > including /etc/profile.d/guix.sh) to run the guix pull and guix install. > > > > Don't forget to set $XDG_DATA_DIRS as adviced in the Trisquel wiki before > > loging out of the session, or the next opening of MATE session will fail. > > If > > it happens, you can still log in to a text session and do the settings as > > explained in the wiki, then log out and log in again. > > > I fogot to add: > > - if you have doubts whether the variables are set properly or not, check > "which guix". If it says it is ~/.config/guix/current/bin/guix, then > everything should be ok. If it is /usr/bin/guix, the variables are not set > properly, log out and log in again and recheck. "which guix" says /home/hagbard/.config/guix/current/bin/guix "guix upgrade" gave hagbard@ckup:~/Opstk/obt/Emacs/emacs-30.1-obtdrk$ guix upgrade guix upgrade: warning: Consider running 'guix pull' followed by 'guix package -u' to get up-to-date packages and security updates. "guix package -u" gave hagbard@ckup:~/Opstk/obt/Emacs/emacs-30.1-obtdrk$ guix package -u guix package: warning: Consider running 'guix pull' followed by 'guix package -u' to get up-to-date packages and security updates. And "guix install emacs-next" only installed The following package will be installed: emacs-next 28.0.50-0.2ea3466 > - if you did not run "guix pull" (without sudo) before installing emacs (or > other packages), all what you will install are versions from the times the > guix Trisquel package was made. If you did that, run "guix pull" and then > "guix upgrade", then you should have the latest emacs. > > > -- > David Lecompte [email protected] ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
Sent with Proton Mail secure email. On Saturday, May 31st, 2025 at 2:58 AM, David Lecompte wrote: > > Have run 'guix install emacs' which installed 'emacs 27.2'. > > > > Finally guix gave the hint below > > > > hint: Consider setting the necessary environment variables by running: > > > > GUIX_PROFILE="/home/hagbard/.guix-profile" > > . "$GUIX_PROFILE/etc/profile" > > > > How would the hint be implemented in my .bashrc file? > > > > Like so: > > > > GUIX_PROFILE="/home/hagbard/.guix-profile" > > > > ## > > ## source "$GUIX_PROFILE/etc/profile" # or the command K2 > > . "$GUIX_PROFILE/etc/profile" # K2 > > > If you use Trisquel with MATE, all the necessary variables are set at login, > there is no need to follow these advices. So you can simply log out and log > in and they will be set properly, or you can run "bash -l" as advised in the > wiki (-l stands for login, so that files in /etc/profile.d are sourced, > including /etc/profile.d/guix.sh) to run the guix pull and guix install. > > Don't forget to set $XDG_DATA_DIRS as adviced in the Trisquel wiki before > loging out of the session, or the next opening of MATE session will fail. If > it happens, you can still log in to a text session and do the settings as > explained in the wiki, then log out and log in again. Things are working well as you describe. Nonetheless, I can only see 27.2, which could mean the new version 30.1 hasn't landed in the Guix channel yet. ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
Le vendredi 30 mai 2025 à 16:58 +0200, David Lecompte a écrit : > > > > Have run 'guix install emacs' which installed 'emacs 27.2'. > > > > Finally guix gave the hint below > > > > hint: Consider setting the necessary environment variables by running: > > > > GUIX_PROFILE="/home/hagbard/.guix-profile" > > . "$GUIX_PROFILE/etc/profile" > > > > > > How would the hint be implemented in my .bashrc file? > > > > Like so: > > > > GUIX_PROFILE="/home/hagbard/.guix-profile" > > > > ## > > ## source "$GUIX_PROFILE/etc/profile" # or the command K2 > > . "$GUIX_PROFILE/etc/profile" # K2 > > > > > > If you use Trisquel with MATE, all the necessary variables are set at > login, > there is no need to follow these advices. So you can simply log out and > log > in and they will be set properly, or you can run "bash -l" as advised in > the > wiki (-l stands for login, so that files in /etc/profile.d are sourced, > including /etc/profile.d/guix.sh) to run the guix pull and guix install. > > Don't forget to set $XDG_DATA_DIRS as adviced in the Trisquel wiki before > loging out of the session, or the next opening of MATE session will fail. > If > it happens, you can still log in to a text session and do the settings as > explained in the wiki, then log out and log in again. > I fogot to add: - if you have doubts whether the variables are set properly or not, check "which guix". If it says it is ~/.config/guix/current/bin/guix, then everything should be ok. If it is /usr/bin/guix, the variables are not set properly, log out and log in again and recheck. - if you did not run "guix pull" (without sudo) before installing emacs (or other packages), all what you will install are versions from the times the guix Trisquel package was made. If you did that, run "guix pull" and then "guix upgrade", then you should have the latest emacs. -- David Lecompte ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
> > Have run 'guix install emacs' which installed 'emacs 27.2'. > > Finally guix gave the hint below > > hint: Consider setting the necessary environment variables by running: > > GUIX_PROFILE="/home/hagbard/.guix-profile" > . "$GUIX_PROFILE/etc/profile" > > > How would the hint be implemented in my .bashrc file? > > Like so: > > GUIX_PROFILE="/home/hagbard/.guix-profile" > > ## > ## source "$GUIX_PROFILE/etc/profile" # or the command K2 > . "$GUIX_PROFILE/etc/profile" # K2 > > If you use Trisquel with MATE, all the necessary variables are set at login, there is no need to follow these advices. So you can simply log out and log in and they will be set properly, or you can run "bash -l" as advised in the wiki (-l stands for login, so that files in /etc/profile.d are sourced, including /etc/profile.d/guix.sh) to run the guix pull and guix install. Don't forget to set $XDG_DATA_DIRS as adviced in the Trisquel wiki before loging out of the session, or the next opening of MATE session will fail. If it happens, you can still log in to a text session and do the settings as explained in the wiki, then log out and log in again. ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
> On Friday, May 30th, 2025 at 10:28 PM, David Lecompte [email protected] > wrote: > > > > > One suggestion could be to use the Guix package manager available at > > > > Trisquel. Have run 'guix install emacs' which installed 'emacs 27.2'. Finally guix gave the hint below hint: Consider setting the necessary environment variables by running: GUIX_PROFILE="/home/hagbard/.guix-profile" . "$GUIX_PROFILE/etc/profile" How would the hint be implemented in my .bashrc file? Like so: GUIX_PROFILE="/home/hagbard/.guix-profile" ## ## source "$GUIX_PROFILE/etc/profile" # or the command K2 . "$GUIX_PROFILE/etc/profile" # K2 ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
Sent with Proton Mail secure email. On Friday, May 30th, 2025 at 10:28 PM, David Lecompte wrote: > > > One suggestion could be to use the Guix package manager available at > > > Trisquel. > > > > I shall look into the capability very closely. > > > On every non-headless Trisquel machine I install for myself or someone else, > I install guix. One reason is to have ungoogled-chromium, as it happens that > a few important websites are not functional enough with abrowser. > > I follow exactly the procedure in the Trisquel wiki for this (there is a > link to it from the "All manuals" page), on Trisquel with MATE environement. > I have used guix once succesfully with KDE on wayland but I recall that some > extra things were needed as KDE did not use /etc/profile.d/guix.sh installed > by the guix package. I should try this again and add to the wiki the extra > configuration needed. > > Two things to note: > - there have been slow response from savannah when running "guix pull", > often getting a 504 error in response. In this case, retrying until it works > can be a solution. However, there is a mirror (which may become or already > have become the main repository, but I did not follow the discussions) on > codeberg which was much faster recently. To use it, add "-- > url=https://codeberg.org/guix/guixhttps://codeberg.org/guix/guix"; after > "guix pull". > - when running "guix install package_xxx" or "guix upgrade", if there are no > substitutes (pre-built binaries) available for some needed packages, your > computer will try building them. If this is ungoogled-chromium, on my > machines, it typically takes several days, if it ever succeeds at all. If > that happens, I just do Control+C to interrupt it and wait a few days before > retrying. It is possible to only upgrade specific packages by running "guix > upgrade package-xxx package-yyy". > > Have a good time with Guix on Trisquel ! Have done guix install emacs But that gets emacs-27.2 to be installed, not emacs-30.1 > However, if you use Parabola, you very quickly have the most up-to-date > version of packages. I regularly travel with a computer with Parabola as > only distro installed, it is fine as a daily driver. > > In my opinion, the main drawbacks of Parabola are that: > - Parabola installation is not automatic, you need to do basic configuration > according to the wiki and think of installing all the packages you need > (like the right xorg driver, that I tend to forget), it took me a bit of > time to get it working for the first time, but then it is fine as a daily > driver. You could try it with a virtual maching in Trisquel. To make your > life a little easier, use the systemd option, at least until you get > familiar enough with Parabola. > - It regularly happens that system upgrade (which one should normally do > before installing any package) is not possible, often because some package > in the "libre" repository (from Parabola) needs to be rebuilt due to some > package upgrade in archlinux repositories (used by Parabola). Any failure of > system upgrade should be reported so that Parabola developers are aware and > fix it. Check the issues marked "sticky" and if any matches with your > problem, add a comment to it, otherwise check "recent issues" and if none > matches with your problem, create a bug report. > > -- > David Lecompte [email protected] ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
On Friday, May 30th, 2025 at 10:28 PM, David Lecompte wrote: > > > One suggestion could be to use the Guix package manager available at > > > Trisquel. > > > > I shall look into the capability very closely. > > > On every non-headless Trisquel machine I install for myself or someone else, > I install guix. One reason is to have ungoogled-chromium, as it happens that > a few important websites are not functional enough with abrowser. > > I follow exactly the procedure in the Trisquel wiki for this (there is a > link to it from the "All manuals" page), on Trisquel with MATE environement. > I have used guix once succesfully with KDE on wayland but I recall that some > extra things were needed as KDE did not use /etc/profile.d/guix.sh installed > by the guix package. I should try this again and add to the wiki the extra > configuration needed. > > Two things to note: > - there have been slow response from savannah when running "guix pull", > often getting a 504 error in response. In this case, retrying until it works > can be a solution. However, there is a mirror (which may become or already > have become the main repository, but I did not follow the discussions) on > codeberg which was much faster recently. To use it, add "-- > url=https://codeberg.org/guix/guixhttps://codeberg.org/guix/guix"; after > "guix pull". > - when running "guix install package_xxx" or "guix upgrade", if there are no > substitutes (pre-built binaries) available for some needed packages, your > computer will try building them. If this is ungoogled-chromium, on my > machines, it typically takes several days, if it ever succeeds at all. If > that happens, I just do Control+C to interrupt it and wait a few days before > retrying. It is possible to only upgrade specific packages by running "guix > upgrade package-xxx package-yyy". > > Have a good time with Guix on Trisquel ! I am seriously looking at the guix package manager, but not yet up to speed with the procedure involved in installing the latest emacs (emacs-30.1) from the current emacs-27.1. > However, if you use Parabola, you very quickly have the most up-to-date > version of packages. I regularly travel with a computer with Parabola as > only distro installed, it is fine as a daily driver. Have had difficulty figuring out what parabola download to use when looking at https://wiki.parabola.nu/Get_Parabola > In my opinion, the main drawbacks of Parabola are that: > - Parabola installation is not automatic, you need to do basic configuration > according to the wiki and think of installing all the packages you need > (like the right xorg driver, that I tend to forget), it took me a bit of > time to get it working for the first time, but then it is fine as a daily > driver. You could try it with a virtual maching in Trisquel. To make your > life a little easier, use the systemd option, at least until you get > familiar enough with Parabola. > - It regularly happens that system upgrade (which one should normally do > before installing any package) is not possible, often because some package > in the "libre" repository (from Parabola) needs to be rebuilt due to some > package upgrade in archlinux repositories (used by Parabola). Any failure of > system upgrade should be reported so that Parabola developers are aware and > fix it. Check the issues marked "sticky" and if any matches with your > problem, add a comment to it, otherwise check "recent issues" and if none > matches with your problem, create a bug report. > > -- > David Lecompte [email protected] ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
> > One suggestion could be to use the Guix package manager available at > > Trisquel. > > I shall look into the capability very closely. > On every non-headless Trisquel machine I install for myself or someone else, I install guix. One reason is to have ungoogled-chromium, as it happens that a few important websites are not functional enough with abrowser. I follow exactly the procedure in the Trisquel wiki for this (there is a link to it from the "All manuals" page), on Trisquel with MATE environement. I have used guix once succesfully with KDE on wayland but I recall that some extra things were needed as KDE did not use /etc/profile.d/guix.sh installed by the guix package. I should try this again and add to the wiki the extra configuration needed. Two things to note: - there have been slow response from savannah when running "guix pull", often getting a 504 error in response. In this case, retrying until it works can be a solution. However, there is a mirror (which may become or already have become the main repository, but I did not follow the discussions) on codeberg which was much faster recently. To use it, add "-- url=https://codeberg.org/guix/guixhttps://codeberg.org/guix/guix"; after "guix pull". - when running "guix install package_xxx" or "guix upgrade", if there are no substitutes (pre-built binaries) available for some needed packages, your computer will try building them. If this is ungoogled-chromium, on my machines, it typically takes several days, if it ever succeeds at all. If that happens, I just do Control+C to interrupt it and wait a few days before retrying. It is possible to only upgrade specific packages by running "guix upgrade package-xxx package-yyy". Have a good time with Guix on Trisquel ! However, if you use Parabola, you very quickly have the most up-to-date version of packages. I regularly travel with a computer with Parabola as only distro installed, it is fine as a daily driver. In my opinion, the main drawbacks of Parabola are that: - Parabola installation is not automatic, you need to do basic configuration according to the wiki and think of installing all the packages you need (like the right xorg driver, that I tend to forget), it took me a bit of time to get it working for the first time, but then it is fine as a daily driver. You could try it with a virtual maching in Trisquel. To make your life a little easier, use the systemd option, at least until you get familiar enough with Parabola. - It regularly happens that system upgrade (which one should normally do before installing any package) is not possible, often because some package in the "libre" repository (from Parabola) needs to be rebuilt due to some package upgrade in archlinux repositories (used by Parabola). Any failure of system upgrade should be reported so that Parabola developers are aware and fix it. Check the issues marked "sticky" and if any matches with your problem, add a comment to it, otherwise check "recent issues" and if none matches with your problem, create a bug report. -- David Lecompte ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
On Friday, May 30th, 2025 at 10:29 AM, Luis Guzman wrote: > > > En 29/05/25 15:16, Heime escribió: > [...] > > > Alright, let's not ask for the moon just yet - but some of the basics for > > developers: Emacs and GCC. Compiling either from source on Trisquel 11 is > > anything but straightforward right now. > > I understand it can feel a bit daunting at first, but if you’d like to > rebuild > emacs from the sources already in the repositories, here’s a straightforward > way to do it: > > sudo apt build-dep emacs > > apt source emacs > > cd emacs-* > > dpkg-buildpackage -us -uc > > this will build the version currently in the repos. From there, you can start > experimenting with your own changes, or even learn more about the Debian > packaging workflow. > > > Trisquel 11 ships with GCC-12 and Emacs-27.1 - both lagging well behind > > the current GCC-15.1 and Emacs-30.1. Now, I understand we can't always > > have the latest and greatest, and there’s a bit of sense in sticking with > > tried-and-true versions for stability. Still, Trisquel 11 was released > > in March 2023, when Emacs 28.2 was already out. > > That’s actually pretty typical for distributions that follow a point release > model, stability and long-term support tend to take priority over having the > absolute latest versions. > > > > So even at launch, things were a bit behind the curve. > > > > What's more, if you want to build from source, you're in for a bit of a > > slog. The documentation isn’t tailored for Trisquel, and you're left > > piecing together dependencies and workarounds from scraps. > > That’s one of the main trade-offs with Debian-based distributions, most of > the integration work is done up front, so things "just work"™ once installed, > but this usually means you won’t always get the very latest package versions. > Trisquel’s model is closer to Ubuntu LTS and prioritizes reliability. > > > What could you suggest can be done a bit better here? > > One suggestion could be to use the Guix package manager available at Trisquel. I shall look into the capability very closely. > > Maybe not always > > the bleeding edge, but at least make it easier for developers to get up > > and running with newer versions before a major release - especially for > > the essentials like Emacs and GCC. Otherwise, working on development > > ends up much harder than it needs to be. > > Like with most things, the process can seem difficult before you get familiar > with it, but once you’ve built or packaged software a few times, it tends to > feel much more manageable. I had managed to install the latest versions, but it is becoming more cumbersome to do for the current releases. > > Regards > > > > > Regards. > > -- > Luis A. Guzmán G. > http://ark.switnet.org > > Capitulo Mexicano de Software Libre - https://cmxsl.org > Software Libre con raíz ética, acción local y visión nacional. > > Por tu propio bien, y en solidaridad a todos, elige la libertad. > ¡Sé Libre! - https://fsfla.org/selibre/ ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
En 29/05/25 15:16, Heime escribió: [...] Alright, let's not ask for the moon just yet - but some of the basics for developers: Emacs and GCC. Compiling either from source on Trisquel 11 is anything but straightforward right now. I understand it can feel a bit daunting at first, but if you’d like to rebuild emacs from the sources already in the repositories, here’s a straightforward way to do it: sudo apt build-dep emacs apt source emacs cd emacs-* dpkg-buildpackage -us -uc this will build the version currently in the repos. From there, you can start experimenting with your own changes, or even learn more about the Debian packaging workflow. Trisquel 11 ships with GCC-12 and Emacs-27.1 - both lagging well behind the current GCC-15.1 and Emacs-30.1. Now, I understand we can't always have the latest and greatest, and there’s a bit of sense in sticking with tried-and-true versions for stability. Still, Trisquel 11 was released in March 2023, when Emacs 28.2 was already out. That’s actually pretty typical for distributions that follow a point release model, stability and long-term support tend to take priority over having the absolute latest versions. So even at launch, things were a bit behind the curve. What's more, if you want to build from source, you're in for a bit of a slog. The documentation isn’t tailored for Trisquel, and you're left piecing together dependencies and workarounds from scraps. That’s one of the main trade-offs with Debian-based distributions, most of the integration work is done up front, so things "just work"™ once installed, but this usually means you won’t always get the very latest package versions. Trisquel’s model is closer to Ubuntu LTS and prioritizes reliability. What could you suggest can be done a bit better here? One suggestion could be to use the Guix package manager available at Trisquel. Maybe not always the bleeding edge, but at least make it easier for developers to get up and running with newer versions before a major release - especially for the essentials like Emacs and GCC. Otherwise, working on development ends up much harder than it needs to be. Like with most things, the process can seem difficult before you get familiar with it, but once you’ve built or packaged software a few times, it tends to feel much more manageable. Regards Regards. -- Luis A. Guzmán G. http://ark.switnet.org Capitulo Mexicano de Software Libre -https://cmxsl.org Software Libre con raíz ética, acción local y visión nacional. Por tu propio bien, y en solidaridad a todos, elige la libertad. ¡Sé Libre! -https://fsfla.org/selibre/ OpenPGP_0x35AD8DB3BE2C988C.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
On Friday, May 30th, 2025 at 8:49 AM, Luis Guzman wrote: > En 29/05/25 14:27, Heime escribió: > > > As it stands, there are simply too many stumbling blocks. If we want > > people to actually use the tools we're building, we ought to make it > > just a bit easier for them to get started. > > > The point of using a point release distro is that the software is well > tested and configured for that point in time, that's also one of the > reasons is very well stable among the bast repository ecosystem. That's > ~65 thousand packages. > > I've mentioned this before, and old package on a point release distro > like Trisquel, Ubuntu, Debian is not an issue, as long as the package > can continue to provide the function it was doing when it got in the > repo, if that package has some security issues it has to be addressed, > but that doesn't mean it will get updated to the latest, some times, a > single change can fix the issue without disturbing the package, that's > the most advised path, when a new distro release comes out, then we can > have all the new stuff at that point in time. > > For the most part Debian has some great tools and platforms to modify, > (re-)build and compile software, if you take the time to get familiar > with them then you'll notice is much easier than trying to look for > documentation on packages that has not being "debianized" at all. > > So in sum, the tools in place are already simple to follow, I think you > may (or may not ) be missing the potential and work already built-in out > of APT and the Debian building tools, even at the debian folder on any > package on the repo. Jumping out in the dark, sure it might be > overwhelming, but once you are familiar with the process, it's not that > hard. > > That said, if you want always the latest and greatest you can use the > Guix repository, maybe something like Parabola (a rolling release > distro) other than having to compile from source yourself every single > time which might get complex on a LTS release. Alright, let's not ask for the moon just yet - but some of the basics for developers: Emacs and GCC. Compiling either from source on Trisquel 11 is anything but straightforward right now. Trisquel 11 ships with GCC-12 and Emacs-27.1 - both lagging well behind the current GCC-15.1 and Emacs-30.1. Now, I understand we can't always have the latest and greatest, and there’s a bit of sense in sticking with tried-and-true versions for stability. Still, Trisquel 11 was released in March 2023, when Emacs 28.2 was already out. So even at launch, things were a bit behind the curve. What's more, if you want to build from source, you're in for a bit of a slog. The documentation isn’t tailored for Trisquel, and you're left piecing together dependencies and workarounds from scraps. What could you suggest can be done a bit better here? Maybe not always the bleeding edge, but at least make it easier for developers to get up and running with newer versions before a major release - especially for the essentials like Emacs and GCC. Otherwise, working on development ends up much harder than it needs to be. Regards > Regards. > > -- > Luis A. Guzmán G. > http://ark.switnet.org > > Capitulo Mexicano de Software Libre - https://cmxsl.org > Software Libre con raíz ética, acción local y visión nacional. > > Por tu propio bien, y en solidaridad a todos, elige la libertad. > ¡Sé Libre! - https://fsfla.org/selibre/ > > ___ > Trisquel-devel mailing list > [email protected] > https://listas.trisquel.info/mailman/listinfo/trisquel-devel ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
Re: [Trisquel-devel] Installing dependencies for latest emacs and gcc releases
En 29/05/25 14:27, Heime escribió: As it stands, there are simply too many stumbling blocks. If we want people to actually use the tools we're building, we ought to make it just a bit easier for them to get started. The point of using a point release distro is that the software is well tested and configured for that point in time, that's also one of the reasons is very well stable among the bast repository ecosystem. That's ~65 thousand packages. I've mentioned this before, and old package on a point release distro like Trisquel, Ubuntu, Debian is not an issue, as long as the package can continue to provide the function it was doing when it got in the repo, if that package has some security issues it has to be addressed, but that doesn't mean it will get updated to the latest, some times, a single change can fix the issue without disturbing the package, that's the most advised path, when a new distro release comes out, then we can have all the new stuff at that point in time. For the most part Debian has some great tools and platforms to modify, (re-)build and compile software, if you take the time to get familiar with them then you'll notice is much easier than trying to look for documentation on packages that has not being "debianized" at all. So in sum, the tools in place are already simple to follow, I think you may (or may not ) be missing the potential and work already built-in out of APT and the Debian building tools, even at the debian folder on any package on the repo. Jumping out in the dark, sure it might be overwhelming, but once you are familiar with the process, it's not that hard. That said, if you want always the latest and greatest you can use the Guix repository, maybe something like Parabola (a rolling release distro) other than having to compile from source yourself every single time which might get complex on a LTS release. Regards. -- Luis A. Guzmán G. http://ark.switnet.org Capitulo Mexicano de Software Libre - https://cmxsl.org Software Libre con raíz ética, acción local y visión nacional. Por tu propio bien, y en solidaridad a todos, elige la libertad. ¡Sé Libre! - https://fsfla.org/selibre/ OpenPGP_0x35AD8DB3BE2C988C.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
[Trisquel-devel] Installing dependencies for latest emacs and gcc releases
Right, let’s get down to it. I’m installing emacs-30.1 from source, using one of the official mirrors. Now, I know some folks would say, “Why not just grab it from the repositories?”—and, sure, that’s the easy road. But if you want the latest and greatest, or you’re after a bit of fine-tuning, building from source is the way to go. Actually getting Emacs up and running from source on a fresh Trisquel system is trickier than it ought to be. The release notes and INSTALL file are all well and good, but they don’t exactly hand you a ready-made recipe for Trisquel 11 - no simple, copy-paste commands to pull in all the right dependencies You end up playing detective, piecing it together from hints and half-answers. It would be something if Trisquel could provide a straightforward way for users to install the dependencies for the latest development release. Just a clear set of steps, tailored for the distro, so we're not left scratching our head hard or chasing missing packages for days. It's not just Emacs, either. The same goes for GCC and any other bit of kit you might want to build yourself. A bit of coordination between the Emacs team and Trisquel maintainers could save everyone a lot of grief - especially those new to the game. As it stands, there are simply too many stumbling blocks. If we want people to actually use the tools we're building, we ought to make it just a bit easier for them to get started. ___ Trisquel-devel mailing list [email protected] https://listas.trisquel.info/mailman/listinfo/trisquel-devel
