dCore roadmap

[Jason W]

I had taken a poll a while back and the consensus was that dCore made from Ubuntu releases should focus on the LTS and not include the 6 month interim releases.  While I have included the 6 month ones since then to provide the latest release and it's packages, that is not very productive when there are Virtualbox and other kernel modules to be made for that release, startup scripts specific to package versions, etc, just for that Ubuntu repo to be unavailable in a few months. 

So I am going to create new dCore ports from the LTS Ubuntu and Debian releases for future dCore ports.  I want to focus on quality more than quantity.  The existing Debian/Ubuntu dCores will still be available for download and access to thier respective repos.  Though Debian Wheezy has reached it's LTS end of life on May 2018, I have said I would keep dCore-wheezy up as long as it's repo is accessible.   Older dCore ports can be useful for old hardware and will be available for the forseeable future. 

That being said, x86 will be supported as long as it can be.  Debian, no problem.  Ubuntu has not had an LTS x86 installer as of Xenial, but I have both an x86 Bionic and (non-LTS) Cosmic installed to hard drive.  Just depends on Ubuntu in the future in regards to their x86 repo. 

[sm8ps]

Hi Jason

I fully agree with your reasoning. And the 32-bit version is very much appreciated here.

When focusing on the LTS versions, would it make sense to include the backports repositories? I recall that some time ago you added in the security repos. Furthermore, I do not understand the exact usage of the debmirror file but I suppose that the updates repository is taken into consideration, right?

Thank you, as always, for your amazing effort!

[Jason W]

Hi sm8ps.  To include backports would make things like Virtualbox kernel modules a moving target, having to be rebuilt on each Virtualbox version update which happens in backports. 

I would rather backport repos be placed in /opt/debextra for those who want to use them.

 
/opt/debmirror is just where one can specify which Debian/Ubuntu mirror to use, the main one is in there by default. The updates repo can be used in /opt/debextra/ like the backports. 

[sm8ps]

Thanks for the explanation! I see the problem as well as the solution. After trying it out, I shall include this information in the wiki.
Cheers!

[Jason W]

For information, at least until it is in the wiki, to include backports in /opt/debextra/ below are the files and entries.  Replace bionic with which Ubuntu version is appropriate:

/opt/debextra/bionicbackportsmain:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-backports main



/opt/debextra/bionicbackportsmultiverse:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-backports multiverse




/opt/debextra/bionicbackportsrestricted:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-backports restricted



/opt/debextra/bionicbackportsuniverse:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-backports universe



And below for the updates repos:


/opt/debextra/bionicupdatesmain:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-updates main



/opt/debextra/bionicupdatesmultiverse:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-updates multiverse




/opt/debextra/bionicupdatesrestricted:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-updates restricted



/opt/debextra/bionicupdatesuniverse:

Code: [Select]

http://in.archive.ubuntu.com/ubuntu/ bionic-updates universe