emo/xbps
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove asciidoc build dependency, use troff manpages directly.

Browse Source
This commit is contained in:
Juan RP 2010-05-03 21:50:34 +02:00
parent 361a7afa29
commit 1b44e18b35
7 changed files with 509 additions and 358 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
NEWS
View File

@ -1,3 +1,7 @@
xbps-0.6.0 (2010-07-01):
* Removed asciidoc build dependency, simply use the troff manpages.
xbps-0.5.0 (2010-05-01):
* xbps-repo(8): fixed the 'search' target to also match patterns against

1
README
View File

@ -6,7 +6,6 @@ To build this you'll need:
- zlib (development package with static libs)
- openssl (development package with static libs)
- libarchive >= 2.8.0 (development package with static libs)
- asciidoc (to build the manpages)
Optionally to build the API documentation (enabled with BUILD_API_DOCS
make(1) argument):

334
bin/xbps-bin/xbps-bin.8 Normal file
View File

@ -0,0 +1,334 @@
'\" t
.\" Title: xbps-bin
.\" Author: [see the "AUTHORS" section]
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 05/03/2010
.\" Manual: \ \&
.\" Source: \ \&
.\" Language: English
.\"
.TH "XBPS\-BIN" "8" "05/03/2010" "\ \&" "\ \&"
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
xbps-bin \- XBPS command for binary packages
.SH "SYNOPSIS"
.sp
\fBxbps\-bin\fR [\fIoptions\fR] \fItarget\fR [\fIpkgname\fR]
.SH "DESCRIPTION"
.sp
The xbps\-bin(8) command is used to handle binary packages created for the \fBXBPS binary package system\fR\&. You can use it to install, remove, list or show information about any binary package\&. Binary packages can be installed from local (\fIdirectory\fR) or remote repositories (\fIhttp\fR, \fIhttps\fR or \fIftp\fR), see xbps\-repo(8) for information about repositories\&.
.SH "OPTIONS"
.PP
\fB\-c\fR \fIcachedir\fR
.RS 4
Sets the
\fIcache\fR
directory to store downloaded binary packages from remote repositories\&. By default it\(cqs set to
\fI/var/cache/xbps\fR
and it\(cqs always relative to the
\fIroot\fR
directory\&. So if you use a
\fIrootdir\fR
of
\fI/blah\fR, it will become
\fI/blah/cachedir\fR\&.
.RE
.PP
\fB\-f\fR
.RS 4
Used currently in the
\fIpurge\fR,
\fIreconfigure\fR
and
\fIremove\fR
targets\&. If set, package(s) will be reconfigured regardless of its state if working with the
\fIreconfigure target, or to force removal of package files even if its hash doesn\(cqt match in the \'purge\fR
and
\fIremove\fR
targets\&.
.RE
.PP
\fB\-p\fR
.RS 4
Used currently in the
\fIremove\fR
and
\fIautoremove\fR
targets, if enabled after removing a package it is also purged\&.
.RE
.PP
\fB\-r\fR \fIrootdir\fR
.RS 4
Sets the
\fIroot\fR
directory\&. By default the root directory is set to
\fI/\fR\&. Please note that the database directory is always set to
\fI/var/db/xbps\fR
independently of
\fIrootdir\fR\&. So if you use a
\fIrootdir\fR
of
\fI/blah\fR, metadata stuff will go into
\fI/blah/var/db/xbps\fR\&.
.RE
.PP
\fB\-v\fR
.RS 4
Shows verbose messages\&. Useful while installing and removing packages\&.
.RE
.PP
\fB\-y\fR
.RS 4
Assume "yes" to all questions\&. This will bypass all questions and immediately proceed with the task, use this option with care\&.
.RE
.PP
\fB\-V\fR
.RS 4
Shows the current XBPS release version (library and code)\&.
.RE
.SH "TARGETS"
.sp
Please note that all targets are \fBcase insensitive\fR\&.
.PP
\fBautoremove\fR
.RS 4
Removes
\fIleaf\fR
packages\&. These packages were installed as dependencies and currently there is not any package depending on it, directly or indirectly\&. Usually it is safe to always answer
\fIyes\fR\&.
.RE
.PP
\fBautoupdate\fR
.RS 4
Updates all currently installed packages to the most newer version available in repository pool\&.
.RE
.PP
\fBcheck \fR\fB\fIpkgname(s)\fR\fR\fB | \fR\fB\fIall\fR\fR
.RS 4
Checks for integrity errors in installed packages\&. The checks are to found missing run\-time dependencies, missing and modified package files and metadata files\&. If the
\fBall\fR
keyword is used,
\fIall\fR
packages currently installed will be checked, otherwise only
\fBpkgname\fR\&.
.RE
.PP
\fBinstall \fR\fB\fIpkgname(s)\fR\fR\fB | \fR\fB\fIpkgpattern(s)\fR\fR
.RS 4
Install binary package(s) from repository pool by specifying "\fBpkgname(s)\fR" or "\fBpackage pattern(s)\fR"\&. The first repository matching the arguments will be used\&. The package(s) will be
\fIdownload\fR
(if working with a remote repository),
\fIunpacked\fR
and
\fIconfigured\fR\&. The
\fIunpack stage will execute the \fR\fI\fBpre\-install\fR\fR\fI action on its \fR\fI\fBINSTALL\fR\fR\fI script, and unpack its files\&. The \'configure\fR
stage will run the
\fBpost\-install\fR
action set on its
\fBINSTALL\fR
script and will change its state to
\fBinstalled\fR
in the package database\&.
.RE
.PP
\fBlist\fR
.RS 4
Lists all currently installed packages\&.
.RE
.PP
\fBlist\-manual\fR
.RS 4
Lists packages that were installed
\fImanually\fR
by the user, i\&.e not as dependencies of any other package\&.
.RE
.PP
\fBpurge \fR\fB\fIpkgname\fR\fR\fB | \fR\fB\fIall\fR\fR
.RS 4
Purge an installed package,
\fBpkgname\fR
or
\fBall\fR
packages\&. The
\fIpurge\fR
stage runs the
\fBpost\-remove\fR
action set in the
\fBREMOVE\fR
script in its metadata directory ( /var/db/xbps/metadata/\fIpkgname\fR
) and will remove configuration (if they were not modified by the user) and metadata files\&. The package will be fully removed from the system once it has been
\fBpurged\fR\&. If
\fB\-f\fR
option is used, configuration files that have been modified
\fBWILL BE REMOVED, BEWARE WITH THIS!\fR\&.
.RE
.PP
\fBreconfigure \fR\fB\fIpkgname\fR\fR\fB | \fR\fB\fIall\fR\fR
.RS 4
Reconfigure an
\fBunpacked\fR
package\&. Packages in this state are not fully installed, because they were not configured for whatever reason\&. The
\fIconfigure\fR
stage will run the
\fIpost\-install\fR
action set on its
\fBINSTALL\fR
script and will change its state to
\fBinstalled\fR
in the package database\&. The
\fIall\fR
keyword can be used to reconfigure all not configured packages\&. If
\fB\-f\fR
option is used, the package will be reconfigured even if its state is already
\fBinstalled\fR\&.
.RE
.PP
\fBremove \fR\fB\fIpkgname(s)\fR\fR
.RS 4
Removes the installed package
\fIpkgname(s)\fR\&. Its files will be removed and its state will be changed to
\fBconfig\-files\fR
in the package database\&. Configuration files, its metadata directory/files and its information in the package database are preserved\&. To fully remove a package in
\fBconfig\-files\fR
state, it must be
\fBpurged\fR
with the
\fBpurge\fR
command\&. If
\fB\-f\fR
option is used, package files will be removed even if its SHA256 hash doesn\(cqt match\&.
.RE
.PP
\fBshow \fR\fB\fIpkgname\fR\fR
.RS 4
Shows information for installed package
\fIpkgname\fR\&. This will print the size it takes in filesystem, description, maintainer, architecture and other information\&.
.RE
.PP
\fBshow\-deps \fR\fB\fIpkgname\fR\fR
.RS 4
Shows the list of dependencies that
\fIpkgname\fR
requires at run time\&.
.RE
.PP
\fBshow\-files \fR\fB\fIpkgname\fR\fR
.RS 4
Shows the list of files that
\fIpkgname\fR
contains\&.
.RE
.PP
\fBshow\-revdeps \fR\fB\fIpkgname\fR\fR
.RS 4
Shows the reverse dependencies for
\fIpkgname\fR\&. Reverse dependencies are packages that are currently depending in
\fIpkgname\fR
directly\&.
.RE
.PP
\fBupdate \fR\fB\fIpkgname(s)\fR\fR
.RS 4
Updates
\fIpkgname(s)\fR
to the most newer version available in repository pool\&. This can be used if only
\fIpkgname(s)\fR
needs to be updated, unlike the
\fBautoupdate\fR
target that will update all currently installed packages\&.
.RE
.SH "PACKAGE STATES"
.sp
A package can be in a different state while it is being installed, removed, unpacked, configured or purged\&. The following states are available:
.PP
\fBinstalled\fR
.RS 4
The package is fully installed, that means it was unpacked and configured correctly\&.
.RE
.PP
\fBunpacked\fR
.RS 4
The package has been unpacked in destination root directory, but it is not fully installed because it was not yet configured\&. Please note, that some packages will do not work if they are only unpacked\&.
.RE
.PP
\fBconfig\-files\fR
.RS 4
The package has been removed but configuration files and its metadata directory are still available (and it is still registered in the package database)\&. You can
\fIpurge\fR
safely packages that are in this state, modified configuration files will be preserved\&.
.RE
.SH "FILES"
.PP
\fB/var/db/xbps\fR
.RS 4
xbps global
\fImetadata\fR
directory\&.
.RE
.PP
\fB/var/db/xbps/metadata/<pkgname>\fR
.RS 4
Installed package metadata directory\&.
.RE
.PP
\fB/var/db/xbps/metadata/<pkgname>/files\&.plist\fR
.RS 4
Installed package metadata list of files\&.
.RE
.PP
\fB/var/db/xbps/metadata/<pkgname>/prop\&.plist\fR
.RS 4
Installed package metadata properties\&.
.RE
.PP
\fB/var/db/xbps/regpkgdb\&.plist\fR
.RS 4
Registered packages plist database\&.
.RE
.PP
\fB/var/cache/xbps\fR
.RS 4
xbps
\fIcache\fR
directory for downloaded binary packages\&.
.RE
.SH "EXAMPLES"
.PP
\fBInstall a package by specifying its name:\fR
.RS 4
$ xbps\-bin install foo
.RE
.PP
\fBInstall a package by specifying a package pattern:\fR
.RS 4
$ xbps\-bin install "\fBfoo>=3\&.0\fR"
.RE
.PP
\fBInstall multiple packages by specifying names and package patterns:\fR
.RS 4
$ xbps\-bin install foo "\fBblah⇐4\&.0\fR" baz\-2\&.0 "\fBblob>4\&.[0\-9]\fR"
.RE
.SH "BUGS"
.sp
Probably, but I try to make this not happen\&. Use it under your own responsability and enjoy your life\&.
.sp
Report bugs in \fIhttp://code\&.google\&.com/p/xbps\fR\&.
.SH "SEE ALSO"
.sp
xbps\-repo(8), xbps\-src(8)
.sp
The XBPS project: \fIhttp://code\&.google\&.com/p/xbps\fR
.sp
To build binary packages, the xbps\-src(8) shell script is the command designed for this task\&. This must be retrieved from a Mercurial repository, available at \fIhttp://xbps\-src\&.xbps\&.googlecode\&.com/hg/\fR\&.
.SH "AUTHORS"
.sp
The \fBXBPS binary package system\fR has been designed and implemented by Juan Romero Pardines <xtraeme@gmail\&.com>\&.

225
bin/xbps-bin/xbps-bin.8.txt
View File

@ -1,225 +0,0 @@
XBPS-BIN(8)
===========
NAME
----
xbps-bin - XBPS command for binary packages
SYNOPSIS
--------
*xbps-bin* ['options'] 'target' ['pkgname']
DESCRIPTION
-----------
The xbps-bin(8) command is used to handle binary packages created
for the *XBPS binary package system*. You can use it to install, remove,
list or show information about any binary package. Binary packages can
be installed from local ('directory') or remote repositories ('http',
'https' or 'ftp'), see xbps-repo(8) for information about repositories.
OPTIONS
-------
*-c* 'cachedir'::
Sets the 'cache' directory to store downloaded binary packages
from remote repositories.
By default it's set to '/var/cache/xbps' and it's always relative
to the 'root' directory. So if you use a 'rootdir' of '/blah',
it will become '/blah/cachedir'.
*-f*::
Used currently in the 'purge', 'reconfigure' and 'remove' targets.
If set, package(s) will be reconfigured regardless of its state if working
with the 'reconfigure target, or to force removal of package files
even if its hash doesn't match in the 'purge' and 'remove' targets.
*-p*::
Used currently in the 'remove' and 'autoremove' targets, if enabled
after removing a package it is also purged.
*-r* 'rootdir'::
Sets the 'root' directory. By default the root directory is
set to '/'. Please note that the database directory is always
set to '/var/db/xbps' independently of 'rootdir'. So if you
use a 'rootdir' of '/blah', metadata stuff will go into
'/blah/var/db/xbps'.
*-v*::
Shows verbose messages. Useful while installing and removing packages.
*-y*::
Assume "yes" to all questions. This will bypass all questions and
immediately proceed with the task, use this option with care.
*-V*::
Shows the current XBPS release version (library and code).
TARGETS
-------
Please note that all targets are *case insensitive*.
*autoremove*::
Removes 'leaf' packages. These packages were installed as dependencies
and currently there is not any package depending on it, directly or
indirectly. Usually it is safe to always answer 'yes'.
*autoupdate*::
Updates all currently installed packages to the most newer version
available in repository pool.
*check 'pkgname(s)' | 'all'*::
Checks for integrity errors in installed packages. The checks
are to found missing run-time dependencies, missing and modified
package files and metadata files. If the *all* keyword is used,
'all' packages currently installed will be checked, otherwise only
*pkgname*.
*install 'pkgname(s)' | 'pkgpattern(s)'*::
Install binary package(s) from repository pool by specifying
"*pkgname(s)*" or "*package pattern(s)*".
The first repository matching the arguments will be used.
The package(s) will be 'download' (if working with
a remote repository), 'unpacked' and 'configured'. The 'unpack stage will
execute the *pre-install* action on its *INSTALL* script, and unpack its files.
The 'configure' stage will run the *post-install* action set on its
*INSTALL* script and will change its state to *installed* in the
package database.
*list*::
Lists all currently installed packages.
*list-manual*::
Lists packages that were installed 'manually' by the user, i.e
not as dependencies of any other package.
*purge 'pkgname' | 'all'*::
Purge an installed package, *pkgname* or *all* packages. The 'purge'
stage runs the *post-remove* action set in the *REMOVE* script in its
metadata directory ( /var/db/xbps/metadata/'pkgname' ) and will
remove configuration (if they were not modified by the user) and
metadata files. The package will be fully removed from the system once
it has been *purged*. If *-f* option is used, configuration files
that have been modified *WILL BE REMOVED, BEWARE WITH THIS!*.
*reconfigure 'pkgname' | 'all'*::
Reconfigure an *unpacked* package. Packages in this state are not
fully installed, because they were not configured for whatever reason.
The 'configure' stage will run the 'post-install' action set on its
*INSTALL* script and will change its state to *installed* in the
package database. The 'all' keyword can be used to reconfigure all
not configured packages. If *-f* option is used, the package will be
reconfigured even if its state is already *installed*.
*remove 'pkgname(s)'*::
Removes the installed package 'pkgname(s)'. Its files will be removed
and its state will be changed to *config-files* in the package
database. Configuration files, its metadata directory/files and
its information in the package database are preserved. To fully remove
a package in *config-files* state, it must be *purged* with the
*purge* command. If *-f* option is used, package files will be removed
even if its SHA256 hash doesn't match.
*show 'pkgname'*::
Shows information for installed package 'pkgname'. This will print
the size it takes in filesystem, description, maintainer, architecture
and other information.
*show-deps 'pkgname'*::
Shows the list of dependencies that 'pkgname' requires at run time.
*show-files 'pkgname'*::
Shows the list of files that 'pkgname' contains.
*show-revdeps 'pkgname'*::
Shows the reverse dependencies for 'pkgname'. Reverse dependencies
are packages that are currently depending in 'pkgname' directly.
*update 'pkgname(s)'*::
Updates 'pkgname(s)' to the most newer version available in repository
pool. This can be used if only 'pkgname(s)' needs to be updated, unlike
the *autoupdate* target that will update all currently installed
packages.
PACKAGE STATES
--------------
A package can be in a different state while it is being installed, removed,
unpacked, configured or purged. The following states are available:
*installed*::
The package is fully installed, that means it was unpacked and
configured correctly.
*unpacked*::
The package has been unpacked in destination root directory, but
it is not fully installed because it was not yet configured. Please
note, that some packages will do not work if they are only unpacked.
*config-files*::
The package has been removed but configuration files and its metadata
directory are still available (and it is still registered
in the package database). You can 'purge' safely packages that are
in this state, modified configuration files will be preserved.
FILES
-----
*/var/db/xbps*:: xbps global _metadata_ directory.
+
*/var/db/xbps/metadata/<pkgname>*:: Installed package metadata directory.
+
*/var/db/xbps/metadata/<pkgname>/files.plist*:: Installed package metadata list of files.
+
*/var/db/xbps/metadata/<pkgname>/prop.plist*:: Installed package metadata properties.
+
*/var/db/xbps/regpkgdb.plist*:: Registered packages plist database.
+
*/var/cache/xbps*:: xbps _cache_ directory for downloaded binary packages.
+
EXAMPLES
--------
*Install a package by specifying its name:*::
$ xbps-bin install foo
*Install a package by specifying a package pattern:*::
$ xbps-bin install "*foo>=3.0*"
*Install multiple packages by specifying names and package patterns:*::
$ xbps-bin install foo "*blah<=4.0*" baz-2.0 "*blob>4.[0-9]*"
BUGS
----
Probably, but I try to make this not happen. Use it under your own
responsability and enjoy your life.
Report bugs in '<http://code.google.com/p/xbps>'.
SEE ALSO
--------
link:xbps-repo.8.html[xbps-repo(8)], link:xbps-src.8.html[xbps-src(8)]
The XBPS project: '<http://code.google.com/p/xbps>'
To build binary packages, the xbps-src(8) shell script is the command
designed for this task. This must be retrieved from a Mercurial repository,
available at '<http://xbps-src.xbps.googlecode.com/hg/>'.
AUTHORS
-------
The *XBPS binary package system* has been designed and implemented by
Juan Romero Pardines <xtraeme@gmail.com>.

169
bin/xbps-repo/xbps-repo.8 Normal file
View File

@ -0,0 +1,169 @@
'\" t
.\" Title: xbps-repo
.\" Author: [see the "AUTHORS" section]
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 05/03/2010
.\" Manual: \ \&
.\" Source: \ \&
.\" Language: English
.\"
.TH "XBPS\-REPO" "8" "05/03/2010" "\ \&" "\ \&"
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
xbps-repo \- XBPS command for binary package repositories
.SH "SYNOPSIS"
.sp
\fBxbps\-repo\fR [\fIoptions\fR] \fItarget\fR [\fIarguments\fR]
.SH "DESCRIPTION"
.sp
The xbps\-repo(8) command is used to handle local or remote binary package repositories in the \fBXBPS binary package system\fR\&. You can use it to create a package index for a local repository, add or remove local and remote repositories, search for packages and show information about a binary package in repository pool\&.
.SH "OPTIONS"
.PP
\fB\-c\fR \fIcachedir\fR
.RS 4
Sets the
\fIcache\fR
directory to store downloaded binary packages from remote repositories\&. By default it\(cqs set to
\fI/var/cache/xbps\fR
and it\(cqs always relative to the
\fIroot\fR
directory\&. So if you use a
\fIrootdir\fR
of
\fI/blah\fR, it will become
\fI/blah/cachedir\fR\&.
.RE
.PP
\fB\-r\fR \fIrootdir\fR
.RS 4
Sets the
\fIroot\fR
directory\&. By default the root directory is set to
\fI/\fR\&. Please note that the database directory is always set to
\fI/var/db/xbps\fR
independently of
\fIrootdir\fR\&. So if you use a
\fIrootdir\fR
of
\fI/blah\fR, metadata stuff will go into
\fI/blah/var/db/xbps\fR\&.
.RE
.PP
\fB\-V\fR
.RS 4
Shows the current XBPS release version (library and code)\&.
.RE
.SH "TARGETS"
.sp
Please note that all targets are \fBcase insensitive\fR\&.
.PP
\fBadd\fR \fIURI\fR
.RS 4
Adds a repository as specified in
\fIURI\fR
to the repository pool\&. Local (by specifying a
\fBdirectory\fR) and remote (by specifiying an
\fBHTTP/HTTPS/FTP URL\fR) repositories can be specified\&.
.RE
.PP
\fBgenindex\fR \fI/path/to/local/repo\fR
.RS 4
Generates a package index for a local repository as specified in its argument\&. It will look for archives with
\fB\&.xbps\fR
extension and will only add it into the index if version is newer than the one available in the index\&. If a newer package is available, the for old package file will be removed automatically\&.
.RE
.PP
\fBlist\fR
.RS 4
Lists all currently registered repositories in repository pool\&.
.RE
.PP
\fBremove\fR \fIURI\fR
.RS 4
Removes a repository from repository pool as specified by the
\fIURI\fR
argument\&. You have to use the same
\fIURI\fR
that was used in the
\fBadd\fR
target\&.
.RE
.PP
\fBsearch\fR \fIpattern\fR
.RS 4
Search for packages containing the shell
\fIpattern\fR
(see fnmatch(3)) in its
\fBpkgname\fR
or
\fBdescription\fR
values in repository pool\&.
.RE
.PP
\fBshow \fR\fB\fIpkgname\fR\fR
.RS 4
Shows information about binary package
\fIpkgname\fR\&. This will print the size it takes in filesystem, description, maintainer, architecture and other information\&. The first repository in the pool wins\&.
\fBNOTE: if a remote repository is the winner and binary package is not available in cachedir, it will fetch remotely and \fR\fB\fIon\-the\-fly\fR\fR\fB the info\fR\&.
.RE
.PP
\fBshow\-deps \fR\fB\fIpkgname\fR\fR
.RS 4
Shows run time dependencies for binary package
\fIpkgname\fR\&. The first repository in the pool wins\&.
.RE
.PP
\fBshow\-files \fR\fB\fIpkgname\fR\fR
.RS 4
Shows the file list for a binary package
\fIpkgname\fR
by searching it in repository pool\&. The first repository in the pool wins\&.
\fBNOTE: if a remote repository is the winner and binary package is not available in \fR\fBcachedir\fR\fB, it will fetch remotely and \fR\fB\fIon\-the\-fly\fR\fR\fB the info\fR\&.
.RE
.PP
\fBsync\fR
.RS 4
Syncs the package index file for all registered remote repositories\&. The new file will be fetched if local and remote size/mtime do not match\&.
.RE
.SH "FILES"
.PP
\fB/var/db/xbps/repositories\&.plist\fR
.RS 4
Registered repository list\&.
.RE
.PP
\fB/var/db/xbps/<remoterepodir>/pkg\-index\&.plist\fR
.RS 4
Remote repository package index file\&.
.RE
.PP
\fB/var/cache/xbps\fR
.RS 4
xbps
\fIcache\fR
directory for downloaded binary packages\&.
.RE
.SH "BUGS"
.sp
Probably, but I try to make this not happen\&. Use it under your own responsability and enjoy your life\&.
.sp
Report bugs in \fIhttp://code\&.google\&.com/p/xbps\fR\&.
.SH "SEE ALSO"
.sp
xbps\-bin(8), xbps\-src(8)
.sp
The XBPS project: \fIhttp://code\&.google\&.com/p/xbps\fR
.sp
To build binary packages, the xbps\-src(8) shell script is the command designed for this task\&. This must be retrieved from a Mercurial repository, available at \fIhttp://xbps\-src\&.xbps\&.googlecode\&.com/hg/\fR\&.
.SH "AUTHORS"
.sp
The \fBXBPS binary package system\fR has been designed and implemented by Juan Romero Pardines <xtraeme@gmail\&.com>\&.

125
bin/xbps-repo/xbps-repo.8.txt
View File

@ -1,125 +0,0 @@
XBPS-REPO(8)
===========
NAME
----
xbps-repo - XBPS command for binary package repositories
SYNOPSIS
--------
*xbps-repo* ['options'] 'target' ['arguments']
DESCRIPTION
-----------
The xbps-repo(8) command is used to handle local or remote binary
package repositories in the *XBPS binary package system*.
You can use it to create a package index for a local repository,
add or remove local and remote repositories, search for packages
and show information about a binary package in repository pool.
OPTIONS
-------
*-c* 'cachedir'::
Sets the 'cache' directory to store downloaded binary packages
from remote repositories.
By default it's set to '/var/cache/xbps' and it's always relative
to the 'root' directory. So if you use a 'rootdir' of '/blah',
it will become '/blah/cachedir'.
*-r* 'rootdir'::
Sets the 'root' directory. By default the root directory is
set to '/'. Please note that the database directory is always
set to '/var/db/xbps' independently of 'rootdir'. So if you
use a 'rootdir' of '/blah', metadata stuff will go into
'/blah/var/db/xbps'.
*-V*::
Shows the current XBPS release version (library and code).
TARGETS
-------
Please note that all targets are *case insensitive*.
*add* 'URI'::
Adds a repository as specified in 'URI' to the repository pool.
Local (by specifying a *directory*) and remote (by specifiying an
*HTTP/HTTPS/FTP URL*) repositories can be specified.
*genindex* '/path/to/local/repo'::
Generates a package index for a local repository as specified in
its argument. It will look for archives with *.xbps* extension
and will only add it into the index if version is newer than the one
available in the index. If a newer package is available, the
for old package file will be removed automatically.
*list*::
Lists all currently registered repositories in repository pool.
*remove* 'URI'::
Removes a repository from repository pool as specified by the
'URI' argument. You have to use the same 'URI' that was used
in the *add* target.
*search* 'pattern'::
Search for packages containing the shell 'pattern' (see fnmatch(3)) in
its *pkgname* or *description* values in repository pool.
*show 'pkgname'*::
Shows information about binary package 'pkgname'. This will print
the size it takes in filesystem, description, maintainer, architecture
and other information. The first repository in the pool wins. *NOTE:
if a remote repository is the winner and binary package is not available
in cachedir, it will fetch remotely and __on-the-fly__ the info*.
*show-deps 'pkgname'*::
Shows run time dependencies for binary package 'pkgname'. The first
repository in the pool wins.
*show-files 'pkgname'*::
Shows the file list for a binary package 'pkgname' by searching it
in repository pool. The first repository in the pool wins. *NOTE:
if a remote repository is the winner and binary package is not
available in `cachedir`, it will fetch remotely and __on-the-fly__
the info*.
*sync*::
Syncs the package index file for all registered remote repositories.
The new file will be fetched if local and remote size/mtime do not match.
FILES
-----
*/var/db/xbps/repositories.plist*:: Registered repository list.
+
*/var/db/xbps/<remoterepodir>/pkg-index.plist*:: Remote repository package index file.
+
*/var/cache/xbps*:: xbps _cache_ directory for downloaded binary packages.
+
BUGS
----
Probably, but I try to make this not happen. Use it under your own
responsability and enjoy your life.
Report bugs in '<http://code.google.com/p/xbps>'.
SEE ALSO
--------
link:xbps-bin.8.html[xbps-bin(8)], link:xbps-src.8.html[xbps-src(8)]
The XBPS project: '<http://code.google.com/p/xbps>'
To build binary packages, the xbps-src(8) shell script is the command
designed for this task. This must be retrieved from a Mercurial repository,
available at '<http://xbps-src.xbps.googlecode.com/hg/>'.
AUTHORS
-------
The *XBPS binary package system* has been designed and implemented by
Juan Romero Pardines <xtraeme@gmail.com>.

9
prog.mk
View File

@ -3,12 +3,11 @@ CFLAGS += -fPIE
LDFLAGS += -lxbps
.PHONY: all
all: $(BIN) $(BIN).static $(MAN)
all: $(BIN) $(BIN).static
.PHONY: clean
clean:
-rm -f $(BIN) $(MAN)
-rm -f $(BIN).static
-rm -f $(BIN) $(BIN).static
-rm -f $(OBJS)
.PHONY: install
@ -33,10 +32,6 @@ endif
@printf " [CC]\t\t$@\n"
@$(CC) $(CPPFLAGS) $(CFLAGS) -c $<
$(MAN):
@printf " [ASCIIDOC]\t$(MAN)\n"
@a2x -f manpage $(MAN).txt
$(BIN).static: $(OBJS)
@printf " [CCLD]\t\t$@\n"
@$(CC) -static $^ $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) \