[nutyx-annonce] NuTyX 10.0-rc1 Available

[Thierry Nuttens <tnuttens@xxxxxxxxx>]

NuTyX 10.0-rc1 available with cards 2.3.106

The NuTyX team is please to annonce the first release canditate of the next NuTyX 10.0.

NuTyX 10.0-rc1 comes with:

kernel LTS 4.14.10
glibc 2.26
gcc 7.2.0
binutils 2.29.1
cards 2.3.106
python 3.6.3,
xorg-server 1.19.5
qt 5.10.0
KDE plasma 5.11.4, Framework 5.41.0, Applications 17.12.0
gnome shell 3.26.2
mate 1.18.2
lxqt 0.12.0
xfce4 4.12.4
firefox 57.0.3 Quantum
Libreoffice 5.4.4

If we take in consideration all the GIT projects, we did more then 6000 commits on the development branch since the 9.1 version.

Fixed bugs and added functionalities

The live mode of the installer works fines, it has been improved since you don't need too much memory on your machine. (2GB RAM or more is best).

The 'live' can be installed directly on your machine.

The gnome interface is available again, thanks to our contributor Remy for building it.

For users:

- One ISO:

A new Iso is available in 64 bits.

Italian translation of the installer is now complete.

A 966 MB ISO in size containing the base system and MATE 1.18.2. is available.

- flcards: The new graphical packages manager

No need to use the command line for searching, installing or removing packages.

flcards is now able to install directly a graphical interface, you can choose between lxde, lxqt, mate, gnome, kde5 and xfce4.

A GUI is now available for all thoses tasks.

The ISO containing the Xorg graphical server is coming with the flcards package manager so it's possible to make the post-installation in graphical mode

Flcards is using administrator rights without password.

If you're agains this rule, get rid of the flcards package and uses the CLI or edit the /etc/sudoers to your fit.

- xorg-app, xorg-font, xorg-proto and xorg packages are now splitted

The xorg meta package is removed. All the Xorg packages are now in separated package. The documentation will be update when final release 10.0 will be available..

- 17 available collections

• base, cli and gui
• cli-extra and gui-extra
• gnome and gnome-extra
• lxde and lxde-extra
• lxqt and lxqt-extra
• mate and mate-extra
• kde5 and kde5-extra
• xfce4 and xfce4-extra

- New Graphical user interfaces

The 'LXQt' graphical interface is now available as well in binaries and then can be installed via the command:

get lxqt lxqt-extra

The 'i3wm' is now available as well in binaries and then can be installed via the command:

get i3wm

The 'enlightenment'graphical interface is now available as well in binaries and then can be installed via the command:

get enlightenment

- Cards new functionalities

The package manager is now taking care of most of the post-installation automatically. As a result, installation of a big set is now even more fast.

- New Branchs concept

After a long reflexion with Pierre B., we decide to propose several 'versions' for the next major release of NuTyX.

Some users prefer to keep NuTyX uptodate, some others don't want to see any update comming when installing something

The next stable version of NuTyX will use 3 differents versions to match every users needs.

• The "stable" branch

  This is the stable version of NuTyX. Every packages are frozen at the time of it's release, only security updates will be apply.

  New packages can still be added

• The "current" branch

  The "base" is frozen, only security updates will be apply.

  The "cli" and "gui" collections will receives updates in cases they are dependencies that need to be update for any final package. Security updates will be apply

  The others collections will get updates as normal.

  The "current" branch stay compatible with the "stable" one, they will be both used for minor updates of NuTyX (10.1, 10.2, etc).

• The "development" (or "master") branch

  It's the main line (master) of the GIT project for every available collections

  The update process is a "rolling release" mode during the all life of the stable version and it's minor versions (about one year)

  Since all updates are very big and very often, the "development" branch is most of the time not compatible with the stable version of NuTyX. In this case merging into the "stable" branch is never possible.

The "stable" and "current" brannchs have a "limited lifetime" corresponding to the lifetime of the stable version of NuTyX at that time.

For contributors:

- install-nutyx Script new functionnalities

The script is able to install a 32 bits NuTyX into a 64 bits host machine.

It's possible to pass the branch to installed via argument.

- build-collection script new functionnalities

The script is now autonomus, it's just need to specify the path of the GIT project in the /etc/fstab file.

The other 3 mounting points use defaults directories if not specified via available variables or via /etc/fstab file.

- Recept news fonctionnalities:

The 'release' variable is optionnal

If the recept of a package is new, it's not needed to specify the release variable. It will be set automatiquement to '1'.

Only if you need to rebuild the package set it to whaterver you want, probably '2'

release=2

The 'build' variable and 'build()' function

If the 'build' variable is properly set, it will automatically set the content of the build() function

Possible values are:

• autotools
• python2
• python3
• xorg
• kde5

If the 'build()' function and the build variable are empty, it will be the default build() function apply to the package.

The 'uptodate' function

The 'uptodate' function can be used by the pkgmk script

It is call up via the '-itd' option of pkgmk script.

This function (if existing and properly set) is checking the upstream source. If the version of the recept is obsolet, it will be printed out.

Services installation

The service installation is now done via the following code:

Example of the 'sshd' service

..
nutyx_version=10.0-rc1
source=(http://downloads.nutyx.org/files/nutyx-${nutyx_version}.tar.xz
        https://....)
build() {
cd ${name}-$version
../configure --prefix=/usr \
--disable-static
...
...
# Service
cd $SRC/nutyx-${nutyx_version}
make DESTDIR=$PKG install-sshd
}

The run_<nom_de_groupe> variable

It is now possible to specify specific dependencies for a sub package.

Example of depencies for the 'devel' sub-package:

run_devel=(glib.devel gtk3.devel)

Obsolets post-intallations

The 'generic' post-installation are now done automaticaly by the package manager directy at the end of the installation transaction.

It's no need to specify them in the ports.

- News names for the GIT projects

The organisation of the NuTyX contributors collections are now form 13 to 17.

The hierarchie have been change as well:

5 SETS:

• The base is in the GIT base-sysV
• cli and gui are in the GIT core
• cli-extra and gui-extra are in the GIT extra
• lxde, lxqt, mate, gnome, kde5, xfce4 graphical interfaces have they own GIT with the same name.
• Packages without source code available is in it's own GIT project nos

For creators:

- Creating an customised ISO

All the commands are now includes.

- Creating a customised NuTyX

The tutorial is more completed.

Knows bugs

They are none major bugs knows today.

Thanks

I wish to tanks my team. It's a great fun to works with you guys.

Thanks a lot for your contribution.

And now ?

If no problems are found, the next stable release 10.0 will be available beginning Februar 2018.