Posted by: Anonymous Coward
on January 18, 2007 03:09 AM
It is very good that they have brought together big and important groups in the Linux community such as Red Hat, Mandriva, Novell, Debian and Ubuntu.
Getting a good cross-distribution package solution and bringing ISV's over are essential to the success for Linux on the desktop.
I think there should be a open standard file format which can be; * Associated with an GUI software that opens the installer and lets you install the software. Think MSI. * Installed from the command line using a CLI software. * Installed using a package management application. * Can be uninstalled via the command line or via a graphical central package management system application. * Files can be extracted from the package without having to install the package.
The implemention of the cli/gui/package-management-system is up to anyone to code, and the user/distro can choose which of these software to run as long as they can handle the standardized package format.
The package should also be able to contain; * Digital signature (optional). * Metadata for name of software, version, license, url and dependency.
It is up to the developer of the software to decide whether his software should support dependency checking/resolution, hashes or metadata and other stuff. It is also up to him to decide in which programming language he want to code it in, and which libraries he want to use, etc.
Learn about Linux
Download Linux
Get Linux help
My opinion
Posted by: Anonymous Coward on January 18, 2007 03:09 AMGetting a good cross-distribution package solution and bringing ISV's over are essential to the success for Linux on the desktop.
I think there should be a open standard file format which can be;
* Associated with an GUI software that opens the installer and lets you install the software. Think MSI.
* Installed from the command line using a CLI software.
* Installed using a package management application.
* Can be uninstalled via the command line or via a graphical central package management system application.
* Files can be extracted from the package without having to install the package.
The implemention of the cli/gui/package-management-system is up to anyone to code, and the user/distro can choose which of these software to run as long as they can handle the standardized package format.
The package should also be able to contain;
* Digital signature (optional).
* Metadata for name of software, version, license, url and dependency.
It is up to the developer of the software to decide whether his software should support dependency checking/resolution, hashes or metadata and other stuff. It is also up to him to decide in which programming language he want to code it in, and which libraries he want to use, etc.
#