Package Details: sc-im 0.7.0-2

Git Clone URL: (read-only, click to copy)
Package Base: sc-im
Description: A spreadsheet program based on SC
Upstream URL:
Licenses: BSD
Conflicts: sc-im-git, scim-spreadsheet
Submitter: Rhinoceros
Maintainer: Rhinoceros (andmarti1424)
Last Packager: Rhinoceros
Votes: 36
Popularity: 0.89
First Submitted: 2015-09-05 01:44
Last Updated: 2020-03-01 07:36

Dependencies (3)

Required by (0)

Sources (3)

Latest Comments

1 2 3 4 5 Next › Last »

seifferth commented on 2020-01-20 12:51

@Tymekm: That's true. yacc is provided by bison, which is part of base-devel. base-devel is assumed as an implicit dependency for building any package (see <>). This is why bison is not included in the makedepends array. Seeing that you don't seem to have bison installed on your system, you might want to run pacman -S base-devel.

[Sorry for cross-posting from sc-im-git, but this may be useful to know here as well.]

Tymekm commented on 2020-01-20 10:52

The build will fail without yacc.

yacc -d gram.y
make: yacc: Command not found
make: *** [Makefile:167: gram.c] Error 127

snake commented on 2019-11-11 23:25

@Rhinoceros It does indeed look like it. Last comment suggests that trouble comes from "shared formulas", but these are so common in speadsheets!

Rhinoceros commented on 2019-11-11 22:54

@snake Looks like this?

snake commented on 2019-11-11 22:49

Did anyone manage to make the --xlsx_readformulas option work? On my system it fails with a segmentation fault.

Rhinoceros commented on 2018-08-16 03:04

@terinjokes That's pretty straightforward for me to do, but I'm surprised that would be reachable and wouldn't be?

terinjokes commented on 2018-08-15 20:27

Do you mind including the patch in the Git repo, rather than fetching it from GitHub? I was having issues fetching it this morning.

Rhinoceros commented on 2018-05-25 10:09

Thanks @tealeaf. Good call. I've patched with the pull request, changing the executable name. Please let me know if it works (I don't use the scim package).

tealeaf commented on 2018-05-25 07:53

Ah, looks like an upstream change:

tealeaf commented on 2018-05-25 07:46

I notice that installing sc-im-git creates a binary at /usr/bin/sc-im, whilst this PKGBUILD produces /usr/bin/scim. Is that a naming change upstream, or has the scim name been implemented here?

The reason I ask is that /usr/bin/scim is a file conflict with the scim input method, which prevented me from installing both.

Looking at github, it does seem that the binary should be sc-im.