Skip to content
Snippets Groups Projects
Ruben Rodriguez's avatar
Ruben Rodriguez authored
Belenos

Greetings, I took the feedback and I changed some things:

1) I added some lines at the beginning to check if the computer handles 3D acceleration: I decided not doing anything at first because I knew that compton-launcher already checks for that but then I realize that If the user is not properly informed, she/he could think it is a bug so I decided to do something about that. Please, could you check the lines 13 and 14? even though I did some tests to make sure it works, I don't have much experience in shell programming to be 100% sure.

2) I decided to take the other way around about treating the user's imput because I felt that it was more intuitive to treat first if compton was running or not and then evaluate the user's action. Don't worry if the user starts or stops compton by their own, the scripts checks if it is running by looking at the computer's processes and I've already took at into account while I was writing it (No complications added, just treat everything normally)

3) I think I went a little bit too far with the comments... But I prefer you to to decide if that was too much.

Thank you for your patience and I hope this is good enough to be included.

See merge request !106
c477472a
History

Introduction

This set of scripts are helpers that modify and compile those packages coming from the Ubuntu upstream which need it. It might be because they contain non-free stuff, references to Ubuntu that need to be changed, or because we want the package to work our way.

This helpers are similar to some of those in the gNewSense builder, we took some ideas and even some lines from them. If you plan to build an Ubuntu derivative of your own, we suggest you to use Builder instead of this helpers.

All packages in this list are in the appropriate blacklist in the repository updater, so they never enter into the repo from upstream and need to be compiled with this helpers and pushed into reprepro. This helpers also need to be run by hand - and the results tested - any time the repo watchdog warns about pending updates from upstream.

To add a package to the list, just copy one - make-apache2 is a good template - and rename it to make-sourcePackageName. To send the file back to us, or to include any modification into the current scripts, use bzr diff and send the output as an attachment to trisquel-devel@listas.trisquel.info. You need to join the mailing list to send messages to it.

Recommendations

  • Take care to use the right sourcePackageName, many source packages produce several binary packages. apt-cache showsrc binary-package can help you.
  • If possible, use sed to replace chains in the upstream source without the need of external files or patches. If you really need to include a file, place it at the DATA/sourcePackageName directory
  • Do not replace all references to Ubuntu in the package, just those that would actually be shown to the user. Avoid replacing copyright statements!
  • Try to write your replacements in a way they might work in future versions of the upstream package. Well written regexps and sed will help with that.
  • Some of this packages require the lsb to match Trisquel values. Edit the /etc/lsb_release accordingly, or run the helpers in a Trisquel box.
  • You can - and maybe should - run this scripts inside a chroot.

Netinstall

Included are the set of scipts used to generate the network installer images found in Trisquel GNU/Linux LTS (version 2.0, 4.0, 6.0... and up). The scripts may not be available for all versions.

To generate the images, we run the following scripts:

  • make-apt-setup
  • make-base-installer
  • make-choose-mirror
  • make-main-menu
  • make-netcfg
  • make-net-retriever
  • make-pkgsel

Then we push the results into the Trisquel repository and run the script make-debian-installer to build the final images.