For full docu see http://ushi.wurstcase.net/local-repo/ or have a look at doc/local-repo.html
usage: local-repo path [options]
This program helps to manage local repositories. Specify the path to the
repository with the first argument. If no option is specified, some repo
information will be printed.
positional arguments:
path path to the repo or the repo name if set up in your
config file '~/.config/local-repo'
optional arguments:
-h, --help show this help message and exit
-a path [path ...], --add path [path ...]
add a package to the repo - path can point to a local
or remote package file, pkgbuild file or pkgbuild
tarball - supported protocols are HTTP(S) and FTP
-A name [name ...], --aur-add name [name ...]
download, build and add a package from the AUR to the
repo
-c, --check run an integrity check
-C, --clear-cache clear the cache
-e, --elephant the elephant never forgets
-f, --force force an operation - use this with -a or --add to
up-/downgrade a package
-F path, --config-file path
use an alternative config file (instead of
'~/.config/local-repo')
-i name [name ...], --info name [name ...]
display info for specified packages
-l, --list list all packages from the repo
-r name [name ...], --remove name [name ...]
remove packages from the repo
-R, --restore restore repo database
-s term, --search term
find packages
-U, --aur-upgrade upgrade all packages in the repo, which are available
in the AUR
-V, --vcs-upgrade upgrade all packages in the repo, which are based on a
VCS and available in the AUR
Please report bugs at: <https://github.com/ushis/local-repo/issues>
One way of creating a repo is to create an empty diretory and add some packages, eg from the AUR using -A.
$ mkdir /tmp/repo
$ local-repo /tmp/repo -A package1 package2 package3
If you already have some packages in a directory, you can use the -R option
$ cd /path/to/packages
$ ls
package1.pkg.tar.xz
package2.pkg.tar.xz
package3.pkg.tar.xz
$ local-repo ./ -R
The default config file is stored in ~/.config/local-repo. See /usr/share/local-repo/config.example if you want to create one or run
$ cp /usr/share/local-repo/config.example ~/.config/local-repo
and edit the file. The coolest feature of the config file is the path option. Write something like this
[myrepo]
path = /srv/http/repo
Now you can type $ local-repo myrepo -l
instead of $ local-repo /srv/http/repo -l
I am very happy about any contribution. The easiest way to contribute is to add a translation.
Go to https://www.transifex.net/projects/p/local-repo/ and translate into your preferred language. Its that easy.
This is a little bit more complicated, but no problem for experienced git users.
-
Fork local-repo and clone it
-
Check out the devel branch
$ cd /path/to/local-repo $ git checkout devel
-
Check if your language already exists.
mylang
is something like 'en' or 'de'$ cd share $ ls translations/ | grep mylang
-
Copy the template into the translations folder. Replace
mylang
by your language. If your language already exists, you should skip this.$ cp messages.pot translations/mylang.po
-
Edit the language file.
-
If you want to test your translation (This would be very nice!), compile the language files and launch the programm. You need to have installed the gettext package for doin this.
$ ./po.sh compile $ ../local-repo path [options]
-
Add, commit and push your changes and send me a pull request. Choose 'devel' as integration branch.
Happy translating!
Copyright (c) 2012 ushi
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.