Projects tagged ‘packager’

Dist::Zilla builds distributions of code to be uploaded to the CPAN. In this respect, it is like ExtUtils::MakeMaker, Module::Build, or Module::Install. Unlike those tools, however, it is not also a ... [More] system for installing code that has been downloaded from the CPAN. Since it's only run by authors, and is meant to be run on a repository checkout rather than on published, released code, it can do much more than those tools, and is free to make much more ludicrous demands in terms of prerequisites. [Less]

The EPP project creates all the package downloads of eclipse.org based on defined user profiles, provides and integrates the EPP Usage Data Collector that collects information about how individuals ... [More] are using the Eclipse platform, and provides a platform that allows the creation of packages (zip/tar downloads) from an update site. [Less]

Get Every Archive from git package Repository. This package contains utilities for building RPM packages from GEAR repositories and managing GEAR repositories.

Packager is the simple package manager for the Syllable Desktop and Syllable Server operating systems. It is written in ORCA, a partial clone of the REBOL programming language.

Builder Our Builder generates our repositories and liveCD. It is a series of bash scripts, which you may retrieve from our SVN Repositry. How To Create Your Own GNULinux Distribution Updating Builder Modifying a New Package Emeta

Builder is the build system for the Syllable Desktop and Syllable Server operating systems, their native applications and third-party software ported to them. Consonant is the new incarnation of ... [More] Builder, written in ORCA, a partial clone of the REBOL language. [Less]

GiftWrap is a hassle-free way to create Ubuntu packages. It is designed for anyone who deals with distributing software - be it theme designers, software developers, or anyone else. In the future, it ... [More] will support updating of existing packages, uploading to PPA's split packages and more. [Less]

Flex based desktop application for packing scrom 1.2 compliance courses. It will ask you for the course folder and specify atleast one sco. After doing so just click publish button to generate a ... [More] SCORM 1.2 complianced package. It also supports saving of package setting file, so in case same entires you require some other time you can simply click open and browse that file. And that is all to prepare for recreating the package. [Less]

RAILS 2.0 READY!Version 1.2.2 released Oct 31, 2007. ChangeLog. WHY BUNDLE-FU IS SPECIALWeb 2.0 sites have lots of tiny javascript/css files, which causes one extra round trip per file to the ... [More] server and back! This is bad! Bundle-fu throws it all up into a big package and sends it out all at once. Bundle-fu can speed your load time up around 50%. It: Does not require a separate config file Automatically regenerates the bundle if you modify an included file, or change the include order. Is easily bypassed by passing "?bundle_fu=false" into your page (including assets separately vs bundled). It does not affect other users of your site, and stays bypassed for the your session only. Bundle-fu makes debugging fun! Is optimized for production mode (only generates the bundle file once when the server is first started). Puts the bundles in javascripts/cache and stylesheets/cache, so it's easy to ignore with subversion. Rewrites relative URLs in your CSS files, so you'll never have broken images. Minimizes your javascripts by default using the Ruby Version of JSMin. Optionally, if you install PackR, it will automatically use that instead. No additional requests on your rails application - bundled files are served as static files. Supports multiple combinations of JS/CSS, using the :name parameter USAGE / INSTALLATIONStep 1Install this plugin git clone git://github.com/timcharper/bundle-fu.git vendor/plugins/bundle-fu && rm -rf vendor/plugins/bundle-fu/.gitStep 2Put the following around your stylesheets/javascripts (note it works with any method of including assets!): <% bundle do %> ... <%= javascript_include_tag "prototype" %> <%= stylesheet_link_tag "basic.css" %> <%= calendar_date_select_includes "red" %> ... <% end %>That's it! HELPGeneral Documentation Read the FAQ and CAVEATS Post to the mailing list OTHER RUBY ON RAILS ASSET BUNDLERSBundle-fu isn't the only Ruby on Rails plug-in that will bundle assets. It simply has a new approach to doing so. Other asset bundling solutions: AssetPackager - Requires a separate config file to work. Option to compress javascript. Rails 2.0 - Very clean implementation. Doesn't rewrite relative CSS urls. Bundles only in production mode. Doesn't bundle includes from asset include helpers from 3rd party plug-ins. No bypass mechanism (though it could be implemented easily). No js minification. Author:Tim C. Harper - irb(main):001:0> ( 'tim_see_harperATgmail._see_om'.gsub('_see_', 'c').gsub('AT', '@') ) [Less]

Welcome to Ivy RoundUpIvy RoundUp is an online Ivy repository meant to be shared by all Ivy users. Instead of hosting Ivy module definition files (ivy.xml files) and artifacts together on the same ... [More] site, this site hosts only the module definition files plus additional meta-data (packager.xml files) that describes how to download and extract the module's artifacts on-demand at the point of use. This new type of repository is made possible by the Packager Resolver, a new Ivy resolver in available Ivy 2.0 that supports downloading, extracting and repackaging artifacts on-demand. The Packager Resolver allows for a clearer separation between two jobs which don't necessarily go together: maintaining Ivy meta-data, and hosting the actual artifacts. The focus of the Ivy RoundUp project is the first task. In addition, it's easy to use the Ivy RoundUp repository's meta-data to build a normal repository containing artifacts. Our goals are: To maintain an Ivy repository that is: Comprehensive: containing all of your favorite stuff Up-to-date: rapid inclusion of newly released software Refined: full use of Ivy's powerful configuration definitions and dependency mappings Self-consistent: consistency in naming with respect to organizations, modules, configurations, and dependencies, according to documented standards and guidelines To facilitate the easy creation of a normal Ivy repository based on the Ivy RoundUp meta-data To grow an active community of maintainers (want to help?) each of whom is motivated by their own personal interest in, and daily use of, the modules they maintain To become the premiere community Ivy repository on the Internet Want to try it out? Install the latest version of Ivy and then configure your ivysettings.xml as described here. Interested in learning more? Join us on the Ivy RoundUp mailing list! Or read how you can help and become a contributor. You can also view the modules contained in Ivy RoundUp so far. [Less]