search

docker-scripts-archived / dev--LTSP

Virtual LTSP server with vagrant and/or docker-scripts.
GNU General Public License v3.0
7 stars 6 forks source link

added ubuntu-edu packages #57

Closed d78ui98 closed 6 years ago

d78ui98 commented 6 years ago

added ubuntu-edu packages on buster branch. These packages are compiled in debian buster

closes #3 #7

d78ui98 commented 6 years ago

Instead of those 4 lines I can also do 

dpkg -i /vagrant/ubuntu-edu-*

this also works. Let me know if I should do this.

dashohoxha commented 6 years ago
dashohoxha commented 6 years ago

Deepanshu, you have added about 60 new files. I understand that you have just copied the source files of the edubuntu package, since this is easier for you.

Although this may work, it seems to me a lot of files. I would prefer something simpler, for example having only these 4 directories: deb/debian-edu-preschool/, deb/debian-edu-primary, deb/debian-edu-secondary, deb/debian-edu-terciary/, where each of these directories has about 4-5 control files.

This may require you to learn how to build deb packages, to understand the structure of control files etc. But that is the point, I want you to learn and to understand deb packages.

Since I don't understand deb packages myself, I am not sure that what I am asking is possible. But I believe there should be an easier way, you don't need 60 files just to build 4 packages.

Maybe you should ask on the mailing list for any good starting tutorial about understanding and building deb packages.

d78ui98 commented 6 years ago

I am not sure that what I am asking is possible.

Yes we can do this. I just have to copy necessary files in 4 different folders. and define packages in the control file(currently all are defined in one). However, it would increase number of files by 30 or more(4 unique rest redundant).

dashohoxha commented 6 years ago

However, it would increase number of files

I am in favor of a minimalist solution, using the least number of files possible, the least configuration fields possible, the least tools possible. For example use no tools other than dpkg-deb for building the debian packages.

akash0x53 commented 6 years ago

+1 for dpkg-deb

d78ui98 commented 6 years ago

I am in favor of a minimalist solution

Agreed. dpkg-deb comes from devscripts package. Other than that we only need equivs to fix the dependencies. Otherwise mk-build-deps will not work.

d78ui98 commented 6 years ago

We are now down to 6 configuration files. 5 are inside debian folder. Any of them cannot be removed. I refered to this recommended guide from mailing list - https://wiki.debian.org/Packaging/Intro

dashohoxha commented 6 years ago

I suggest that you use this Docker container for testing these scripts and config files (and making sure that they work correctly): https://github.com/docker-scripts/debian But you have to replace stretch with buster on the base image: https://github.com/docker-scripts/debian/blob/master/Dockerfile#L1

d78ui98 commented 6 years ago

Sure.

d78ui98 commented 6 years ago

I suggest that you use this Docker container for testing these scripts and config files

yes they work perfectly.

dashohoxha commented 6 years ago

yes they work perfectly.

Did you use the 'debian' container for testing the packages? What programs are installed when you install the package debian-edu-preschool?

dashohoxha commented 6 years ago

We are now down to 6 configuration files. 5 are inside debian folder. Any of them cannot be removed.

But their content can be fixed and improved. For example:

I refered to this recommended guide from mailing list - https://wiki.debian.org/Packaging/Intro

This is a good one. But the ones that I suggested are good as well: https://github.com/docker-scripts/dev--LTSP/issues/7#issuecomment-400156930