Projects tagged ‘rpm’ and ‘yum’

Yum is an automatic updater and package installer/remover for rpm systems. It automatically computes dependencies and figures out what things should occur to install packages. It makes it easier to ... [More] maintain groups of machines without having to manually update each one using rpm. [Less]

Yum-utils is a collection of tools written using the Yum API, to do different kind of yum/rpm related tasks.

Tools for generating live CD's on Fedora based systems including derived distributions such as RHEL, CentOS and others.

yumex is a GUI for the yum package manager, it is written i Python and is using the PyGTK toolkit for GUI Components.

The Smart Package Manager project has the ambitious objective of creating smart and portable algorithms for solving adequately the problem of managing software upgrading and installation. This tool ... [More] works in all major distributions, and will bring notable advantages over native tools currently in use (APT, APT-RPM, YUM, URPMI, etc). [Less]

The new sfs technology solves software dependencies and installation problems. It consists of a unique file that can be mounted as a normal file-system with all really needed libraries and files of ... [More] the specific program. When mounted the sfslauncher will start the application stored into it. The procedure is completely transparent to the end user; Just double click on the "program.sfs" and sfslauncher will do the magic. Starting with version 1.0 we improved the integration: the operating system now knows the "sfs" file type as a native executable file. How does it work?(See the video, download link is at bottom of document) Well, the file "program.sfs" is a squashfs compressed file that can be used as a virtual file system. The .sfs file can be mounted by a daemon in a hidden directory (/.mounted/"SFSprocessID"). Once mounted the file, sfslauncher program will read the executable's name and all the parameters stored into the "parameters" file (a simple text file). Then the sfslauncher will read the description.id file and will execute the executable file. When the user will close the executable (the software into the package) sfslauncher call the daemon and send to him a command called "flush": the daemon will release the thread, unmount the .sfs file and delete the hidden directory. What is NOT contained in the sfs file ?The Desktop environment's libraries and other operating system's native libraries as for example KDE libraries, gtk+2, glib, libc6 and many more. What will contain the .sfs file ?The sfs file contains just the most necessary libraries to perform a correct software execution. These are what we think are the highlight of the SFS Technology:1--Ease of use; 2--Ease of software sharing; 3--The base configuration of the operating system remains unaltered; 4--It allows dynamic library linking; 5--It allows using different version of software; 6--The sfs technology preserve the environment: it work in USER MODE; 7--Operates also in 64 Bit environment; 8--Released under the GNU/GPL license; 9--A version for Linux Mobile (ARM processors) is under development 10-- Can run simultaneously max 256 sfs application!! This project is under develop at page http://code.google.com/p/sfs-technology/ UbuntuItalian forum discussion : http://forum.ubuntu-it.org/index.php?topic=283698.0 NEW VERSION 1.1.0.4 :--Automatically Dependency Handling: This new version allows handling dynamically some dependencies that could not be in a SFS package. If defined, sfslauncher will try to install this not founded dependency by a simple graphical user interface, showing a popup message! --This new version allows Nautilus to associate the icon contained into the SFS executable file to the correspondent SFS , having the same effect as the executables files do on Windows or Macintosh, where each has its own icon. --Make Portable Option: This new option allows you to save the configurations of applications in the same folder where resides the SFS executable file. This directory could be situated on a portable device (like a USB pen) or on a normal root's directory. This option is not enabled by default. --SFS Editor: an editor for the SFS Technology Executable files downloadable from (for i386 and amd64 architectures): http://code.google.com/p/sfs-technology/downloads/list --Some relevant bugs fixed Video that show the SFS Technology at work !: http://sfs-technology.googlecode.com/files/SFS_example_video.ogv Image of some SFS programs: SFS programs make links in the Main menu under Applications-->Other: SFS Settings : For more information about SFS Technology please contact me. This solution is very important to further increase the usability of Linux worldwide. Vincenzo Dentamaro vincenzodentamaro@hotmail.com SFS Technology developer. Technology published under Ubuntu Brainstorm : InstallationSee installation wiki in the wiki page! If you want to test this technology without compile and install it, use the Ubuntu/Debian SFS Technology Repository, add this line to the file /etc/apt/sources.list For i386 architecture: deb http://unixteam.net/sfs-repository-i386 binary/ For amd64 architecture: deb http://unixteam.net/sfs-repository-amd64 binary/ LicenseThis software is GPL v3 compatible Frequently Asked QuestionsCan two SFS executables share their resources? The sfs packages contains only some libraries not provided in a standard Ubuntu installation, for example in a SFS package there will never be gtk+ libraries or system libraries, but only those libraries which that particular program needs to run properly and the library that are not in a normal Linux installation. Furthermore the static and dynamic linking between libraries is guaranteed, because the SFS load the GUI libraries and other important libraries from the standards shared directories (/usr/lib/ for example), rather less common libraries are loaded from the library directory contained in the SFS package, SFS also allow a system for the Dynamic Library Linking, I try to explain with an example how it works: I take 2 programs (programA.sfs and programB.sfs) both containing the same library called libraryX1.so. If the libraryX1.so is contained in the package programA.sfs when we launch the programA.sfs it will be loaded into memory, when we run the prgamB.sfs it will first seek the libraryX1.so into the mounted directory of programmA.sfs and if found this searched library, then do not load back into memory the same library, but will focus on the library already present in RAM, thus saving time of loading and space RAM. So in conclusion, unlike other technologies SFS Technology provides an interaction and a dynamic link between the libraries, does not contain standard libraries already present in a common installation of Ubuntu, is not a replacement for apt, it began as an aid to making using the software easier on Linux. The motto of Ubuntu is "LINUX for Human Beings"; well I think that the SFS Technology is a solution very close to the "Human Beings". Thanks toNicole Monique Angelynn Marquez for the site correction. HackToLive for have noticed bugs and for suggestions provided. [Less]

The goal of this project it to create one-click software installation feature for Linux users, especially for third-party developers to provide easy way of installing their software. Example: user ... [More] clicks on link on web page, wizard appears which guides user through simple steps to add repository, choose what user wants to install (allowing to choose not to install for example docs) and finally installs the application and accompanying packages. User does not have to know what distribution he is using, what package type, how to add keys for digital signing, etc. For more screenshots of wizard, see Screenshots page. What one-click-installer is: Simple way for users to install software without knowing what distribution you use, how to add repositories, keys, etc. Just click on link, click Next, Next, and you are done. For instructions see InstructionsForUsers. Simple way for application developers (also proprietary) of providing their apps to users. For instructions see InstructionsForApplicationDevelopers. Simple way of providing apps to users by third party packagers and loco teams. For instructions see InstructionsForPackagers. Simple way of providing apps to users by distributions. For instructions see InstructionsForDistributions. What one-click-installer is not: Application packaging system like deb, rpm, autopackage, etc. Package repository tool like apt, yum, etc. Package frontend like Synaptic, Adept, Yast package manager, etc. Possibilities created by one-click-installer: Creating web application catalog with immediate installation link, screenshots, comments, etc. Adding links to install necessary software on forums, blogs, web pages, etc. Adding links to install some software on CDs, in distribution welcome pages (for example "Recommended software to install"), etc. Other important features: Supports full localization, both installation files and installer. Integrates with native package management system, so provides automatic updates using distribution update system. If you want to try out One Click Installer, please download and install package from Download section on the right (or you can browse full downloads list). Then, go to ExampleInstallationFiles page to install example applications. Key points of design: This project specifies file format and tools which provide such wizards for specific distributions. For installation and repository management, tools and package formats included in distribution are used, in particular, this project does not specify any new packaging format. File format allows to specify in one file distribution-specific software channels to use for many distributions, keys, package sets , thus user does not have to know what distribution he is using. There is only one file to be clicked. Installation must be possible in localized manner, in native user language, as users not always know English. More information about file format is available on OneClickInstallerFileFormat page. More information about tool implementation is available on OneClickInstallerTool page. Details of current impementation: The tool currently works on Ubuntu using apt archives (should also work on Debian-based systems). We are looking for developers interested in extending the tool to work on other distribution/software channel (for example to handle RPMs using yum on Fedora). The tool is implemented in Python (no compilation necessary) and uses Qt for frontend. The tool is split into frontend and backend, so implementing other frontends is possible. We are looking for developers interested in porting frontend to different toolkit (especially Gtk, text frontend would also be useful). [Less]

subj.