Projects

Synaptic Package Manager

Synaptic is a graphical package management program for apt. It provides the same features as the apt-get command line utility with a GUI front-end based on Gtk+. * Install, remove, upgrade and downgrade single and multiple packages. * Upgrade your whole system. * Manage package ... [More] repositories (sources.list). * Find packages by name, description and several other attributes. * Select packages by status, section, name or a custom filter. * Sort packages by name, status, size or version. * Browse all available online documentation related to a package. * Download the latest changelog of a package. * Lock packages to the current version. * Force the installation of a specifc package version. * Undo/Redo of selections. [Less]

pacapt

An (Arch Linux) pacman-like package manager for some Linux distributions. Actually this Bash script provides a wrapper for system's package manager. Instead of remembering various options/tools on different OSs, you only need a common way to manipulate packages. Not all options of the native ... [More] package manager are ported; the tool only provides a very basic interface to search, install, remove packages, and/or update the system. [Less]

sfs-technology

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 the specific program. When mounted the sfslauncher will start the application stored into it. The ... [More] 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! 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]

Debian Goodies

A collection of small utilities to make the command line life on a Debian based system easier.

Create config data GUI with validation

Config::Model enables a project developer to provide a graphical configuration editor for his users. For this, the developer must describe the structure and constraints of his project's config (i.e. the config model). provided editor: sshd_config editor. Packages are available for Debian and Ubuntu

debgraph

In a large software ecosystem such as Debian Linux, there is the potential for dependencies among software packages to create complex management and technical problems. For example, dependency loops (cycles) in which a package directly or indirectly depends on itself can confuse package management ... [More] tools as they determine the proper order of package installation. debgraph helps developers to solve this problem by enabling generic queries (e.g., "Give me all the nodes that depend on package X") against the graph of packages and thus automating much of the manual labor that is typically involved in resolving dependency problems. To learn more, please download the source distribution and refer to the GettingStarted page in the wiki. [Less]

spiff-integrator

Spiff Integrator is a small but powerful package manager that was written for adding plugin support into applications. It handles packing/unpacking, installation/updates/removal, and dependency management. It was designed to provide a clean API, high security and high scalability. For ... [More] documentation please refer to the README file or the tests included with the package. You may also look at the API documentation. [Less]

slackian

The objective from this project is port Debian package tools (such apt-get, aptitude, dpkg. Other suggestions?) to Slackware, making SlackBuilds and generate native packages.

jpkg-library

DescriptionJpkg is both a library and a set of Apache Ant tasks for building operating system packages. FeaturesCurrently the Debian .deb format is supported. Detailed validation of package fields to be conformant with the Debian package specification for the package features supported by Jpkg. ... [More] Not all Debian package features are supported, only those necessary to generate useful packages. Supports custom package maintainer scripts, backed by Velocity templates. Contains a library called Antidote, which is an attempt to make certain aspects of writing Ant tasks easier, especially dealing with the mutable state of Ant objects and validation of Ant supplied data. Also included is a Java library for working with Unix ar(1) archives. Includes extensive unit tests. UsageBasic pattern for including the Ant task in your build: Most of the common fields are shown in this example. See the full Ant task schema for more details. packagename 1.2 i386 Package description Package Maintainer maintainer@package.com optional misc bin/ 1.4 12.1a Distribution FilesContained within jpkg-bin.zip: jpkg-combined.jar - The Jpkg library and ant tasks as well as all dependencies. antidote.jar - The Antidote library. jpkg-ant.jar - The Jpkg Ant tasks. Depends on the Jpkg library. jpkg-lib.jar - The Jpkg library. Also distributed: jpkg-src.zip - The source bundle, includes javadocs. DependenciesFor both the library and ant tasks: mail-1.4.1.jar commons-io-1.3.2.jar For the library: commons-codec-1.3.jar For the Ant tasks for velocity: commons-collections-3.2.jar velocity-1.5-dev.jar uudecode is a requirement when executing the maintainer scripts on the target machine. For the Antidote library: The Ant runtime. Custom Maintainer ScriptsSee com/threerings/jpkg/ant/dpkg/scripts/standard/HelloWorld.java for an example. If you create any custom TemplateScript classes you will need to do something like the following. Example custom-scripts.xml: Pattern for including the Ant task in your build with custom TemplateScript classes: Release NotesVersion 1.5 - Documentation improvements. Version 1.4 - Allow maintainer scripts to optionally fail quietly. Version 1.3 - Improve script_runner error handling. Version 1.2 - Make the recursive property of the field optional and default to false. Version 1.1 - Fix bug in applying recursive permissions. Version 1.0 - Initial release. AuthorJpkg was written by Jonathan Le Plastrier, based on an original Python implementation by Landon Fuller. It is copyright Three Rings Design and is released under a BSD license. [Less]