Package Details: sc-im-git latest-3

Git Clone URL: https://aur.archlinux.org/sc-im-git.git (read-only, click to copy)
Package Base: sc-im-git
Description: A spreadsheet program based on SC
Upstream URL: https://github.com/andmarti1424/sc-im
Licenses: BSD
Conflicts: sc-im, scim-spreadsheet
Submitter: seifferth
Maintainer: MithicSpirit
Last Packager: MithicSpirit
Votes: 5
Popularity: 0.000000
First Submitted: 2017-03-29 15:23 (UTC)
Last Updated: 2022-02-02 02:37 (UTC)

Dependencies (5)

Required by (0)

Sources (2)

Latest Comments

1 2 Next › Last »

seifferth commented on 2021-05-18 18:37 (UTC)

Sure. You should now be able to push to this repo.

MithicSpirit commented on 2021-05-18 15:14 (UTC)

Commit 110d270 breaks arch.patch as it already sets the default to xclip (instead of tmux), so removing that section from arch.patch fixes it.

If you could make me co-maintainer I could push that fix and the changes I previously stated.

seifferth commented on 2021-05-08 10:51 (UTC)

@MithicSpirit: I actually just copied the PKGBUILD from the sc-im package and the flags were already contained there. I also don't use sc-im much these days, so I might be a little behind on all things concerning this package.

Would you like to be added as a Co-Maintainer of this PKGBUILD? Or to take over maintenance altogether? Then you could simply push those changes, as I see you already tested them.

MithicSpirit commented on 2021-05-08 03:48 (UTC)

I don't think that the MAKEFLAGS need to be overridden in line 19, as this prevents multithreaded compilation (which works fine for me). Also, in line 34, it is possible to not set CC by instead just appending -fcommon to the CFLAGS variable.

seifferth commented on 2020-01-20 12:49 (UTC)

@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 <https://wiki.archlinux.org/index.php/PKGBUILD#makedepends>). 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.

AnarchoJohn commented on 2020-01-20 11:07 (UTC) (edited on 2020-01-20 11:08 (UTC) by AnarchoJohn)

The build will fail without yacc.

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

Rhinoceros commented on 2017-05-09 11:39 (UTC)

That would work for the initial submission of the package, but in my experience, when you update the PKGBUILD, you'll need to bump pkgver to the most recent value, and append -2. Otherwise, package managers such as pacaur don't see the new version as being greater than the installed version, and it's never updated on users' systems.

seifferth commented on 2017-05-09 10:36 (UTC)

I saw that, but I thought it might be quite misleading to set `pkgver` to some revision that won't really be installed in the end. With `pkgver=current` or `pkgver=latest` it's clear that this pkgbuild doesn't install any specific revision. In the forums it was even once suggested to just set it to `0`. [1] Are there any benefits in setting pkgver to the latest revision at the time of creating the pkgbuild? [1]: https://bbs.archlinux.org/viewtopic.php?pid=1263231#p1263231

Rhinoceros commented on 2017-04-29 23:18 (UTC)

Oops, sorry, I forgot to enable notifications. That looks great. However, as per the wiki, > you still need to declare the pkgver variable with the most recent value So the first pkgver variable should be declared as pkgver=0.6.0.r31.g1039b31

1 2 Next › Last »