File URL changed to:
https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/acme-sac/acme-sac_0.14_i386.deb
Search Criteria
Package Details: acme-sac 0.14-2
| Git Clone URL: | https://aur.archlinux.org/acme-sac.git (read-only) |
|---|---|
| Package Base: | acme-sac |
| Description: | Programmer's editor and shell, running over Inferno |
| Upstream URL: | http://code.google.com/p/acme-sac/ |
| Licenses: | |
| Provides: | |
| Submitter: | fmoralesc |
| Maintainer: | fmoralesc |
| Last Packager: | fmoralesc |
| Votes: | 5 |
| Popularity: | 0.017133 |
| First Submitted: | 2013-07-24 03:20 |
| Last Updated: | 2015-08-26 20:29 |
Dependencies (0)
Required by (0)
Sources (1)
Latest Comments
null commented on 2016-09-07 19:58
cosarara97 commented on 2016-05-25 22:36
The .SRCINFO file is out of date, doesn't match the PKGBUILD.
beingdaddy commented on 2015-12-12 09:53
Hello you have not updated the file "/usr/share/applications/acme-sac.desktop" changing the field exec from acme to acme-sac have also forgotten a file swap of "vi/vim" :D other than, that all right, bye
fmoralesc commented on 2015-08-26 22:30
@mehlon, I just did both; renamed the binary and made the x86_64 dependencies explicit.
Anonymous comment on 2015-08-25 20:05
I use both p9p and acme-sac, so I'd say rename the binary.
Also, this package doesn't work on 64-bit without these packages: gcc-multilib lib32-libxext lib32-libx11. Maybe add them as optional dependencies?
fmoralesc commented on 2015-08-12 10:56
@mehlon, Do you think this should conflict with that package or should the binary be renamed?
Anonymous comment on 2015-08-11 16:04
this conflicts with plan9port (/bin/acme)
Anonymous comment on 2015-08-11 16:04
this actually conflicts with plan9port (/bin/acme)
fmoralesc commented on 2015-02-28 17:23
@stovepower I can't reproduce any issue. acme seems to run fine, and the package contents are installed in the /usr/ dir.
stovepower commented on 2015-02-25 04:01
The package has stopped working ever since Arch Linux moved to /usr/bin.
I imagine the executable can't find its dependencies as a result.