| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
While we're here, merge our 'git config' command into the clone.
|
|
just set GIT_DIR appropriately and always operate from the original $PWD.
As part of this, let's cleanup our error handling in initialize() a fair
bit.
|
|
No need to define a whole array for passing -q
|
|
Some packages, e.g. libsigc++-docs, needs to be properly hex-escaped.
|
|
Fixes #22.
|
|
|
|
This removes the use of a tempfile entirely, and only updates the cache
when `git ls-remote` succeeds.
Based on a PR by polygamma:
https://github.com/falconindy/asp/pull/20
|
|
|
|
Closes #17.
|
|
|
|
While we're at it, separate our help output into two sections, since
we're accumulating a growing list of subcommands which operate not on
packages, but on the meta level of the asp repo.
Closes #15.
|
|
We have our nice action__ prefix on all of our action disspatchers, so
let's just use that to our advantage.
While we're here, fix the return code when we encounter an ambiguous
action
|
|
This solves the problem of:
$ asp checkout foo
$ asp list-arches foo
warning: refname 'packages/packages/foo' is ambiguous.
x86_64
i686
Same for list-repos (duh, shared codepath)
|
|
|
|
|
|
bsdtar is common to all Arch systems, but other distros (debian-ish)
might only have tar installed by default. Sadly, bsdtar has slightly
nicer semantics in it's -s than GNU tar's transform when matchin
directories in the tarball.
|
|
This is an implementation detail -- no one should really need to know
or core which repo the package came from. Moreover, there's nothing you
can do with this information. It's conceivable that a package of the
same name could exist in both git repos, but this would be semantically
forbidden by Arch packaging policies, and not well handled by asp
regardless of showing the prefix here.
Fixes GH#14.
|
|
|
|
|
|
The curly braces in '${XDG_CACHE_HOME:-$HOME/.cache}/asp' seem to confuse the parser
|
|
|
|
|
|
Fixup how we do versioning for git builds, and fix the missing package
version in the manpage and the static version in the script.
|
|
|
|
|
|
|
|
|
|
|
|
completions might trigger tracking of a new package. it all goes to
stderr, but let's not crowd the output regardless.
|
|
|
|
|
|
mostly to make shellcheck happy
|
|
Update README.md
|
|
|
|
And keep the doc up to date...
|
|
When a basic lookup fails, attempt to resolve the package name through
archweb to get the pkgbase, under the assumption that this might be a
split package. This adds jq as a new dependency.
Closes #8.
|
|
Others have asked for this in the past, see:
https://github.com/falconindy/asp/issues/7#issuecomment-57004965
https://github.com/falconindy/asp/pull/9
asp might get more traction with the prospect of it more widely
replacing ABS, and I suspect this will come up again.
|
|
Since aceefc28ca701feb8, the manpage has been out of date, not
mentioning new features. While we're here, extend the manpage to better
cover the arguments to our subcommands.
|
|
|
|
pass --prune=all to gc to ensure that we properly cleanup unpacked and
packed objects and don't have the weird bloating effect after a first
pass, e.g.:
$ asp disk-usage
==> Using 640K on disk.
$ asp gc
Nothing new to pack.
$ asp disk-usage
==> Using 8.4M on disk.
$ asp gc
Nothing new to pack.
$ asp disk-usage
==> Using 328K on disk.
|
|
|
|
I'm too stubborn to turn extdebug on, so let's just give up on
BASH_ARGC (which never worked properly because former stubbornness
about extdebug), and just pass $#.
|
|
|
|
|
|
|
|
|
|
|