160 likes | 304 Views
Online Package Repository and Directory Service. As presented by Jim Kring September 2 nd , 2003. Presentation Outline. Release & Acquire steps in the OpenG Process Model Package Repositories Package Directories Package Directory Service. OpenG Development Process.
E N D
Online Package Repository and Directory Service As presented by Jim Kring September 2nd, 2003
Presentation Outline • Release & Acquire steps in the OpenG Process Model • Package Repositories • Package Directories • Package Directory Service OpenG Group Meeting
OpenG Development Process How does this fit into the process? Release • Upload to repository • Register withdirectory Acquire • Locate with directory • Download fromrepository OpenG Group Meeting
What’s a Package Repository? A Package Repository is a place where released packages are made available to users OpenG Group Meeting
Online Package Repository • Released packages are made available over the Internet via a variety of protocols: HTTP, FTP, Local File Path, Network (UNC) File Path. • The URLs of these packages are published via a directory • Collectively these URLs comprise the package repository OpenG Group Meeting
OpenG’s Packages on SourceForge OpenG projects hosted on SourceForge release packages through SF’s package release system • Packages are available at over a dozen mirrors worldwide • Mirrors have predictable URLs OpenG Packages are always online! OpenG Group Meeting
What’s a Package Directory? A Package Directory is a listing of packages. It points to the URLs of packages in the repository. It also points to the URLs of other package directories. OpenG Group Meeting
A “Web” of Packages Package Directory Contains Package URLs Directory URLs OpenG Group Meeting
The “Web” analogy • As Web pages link to other Web pages, package directories link to other package directories • As web pages link to downloadable files, directories link to downloadable packages OpenG Group Meeting
What’s a Package Directory Service? The Package Directory Service is a way of locating packages and directories of packages over a network. To continue the web analogy think of it as a search engine. OpenG Group Meeting
Some Implementation Details • Package Directory Files • Directory Links • Package Cache OpenG Group Meeting
Package Directory File An INI File that looks like the following [Self] Self.Name=OpenG Package Directory Release.Number=1 Release.Date=Jun 1st, 2003 Self.URL=http://openg.org/openg.ogpd Creator.Name=OpenG.org Creator.Email=jkring@openg.org Creator.URL=http://openg.org [Package ogtk_appcontrol-2.0-1] Package.URL=http://openg.org/packages/OGTK 2.x/ogtk_appcontrol-2.0-1.ogp OpenG Group Meeting
Dirs Link to Other Dirs and Pkgs [Directory OpenG Package Directory] Directory.URL=http://openg.org/packages/openg.ogpd [Self] Self.Name=OpenG Package Directory Release.Number=1 Release.Date=Jun 1st, 2003 Self.URL=http://openg.org/openg.ogpd Creator.Name=OpenG.org Creator.Email=jkring@openg.org Creator.URL=http://openg.org [Package ogtk_appcontrol-2.0-1] Package.URL=http://openg.org/packages/OGTK 2.x/ogtk_appcontrol-2.0-1.ogp OpenG Group Meeting
Packages – Acquisition & Installation • Packages are available for download from the Internet and may be copied to a local cache • Once cached, packages may be installed • Once installed, packages may be configured • Installed libraries are included in the VI Namespace and may be added/removed to/from the Dynamic Palette View • Installed resources are made available to dependent resources. The API library of OpenG Group Meeting
OpenG Packages - User Perspective OpenG Group Meeting
Recap • Package Directory Files are similar to Web pages (which link to non-Web page files and other web pages) • The Package Directory Service is a crawler that is able to search within some defined scope for available packages. • Packages are cached locally when downloaded and may be installed or uninstalled to quickly switch between development system and library configurations. OpenG Group Meeting