GramEditor/gram
38
985
Fork
You've already forked gram
88

chore: add binary aur install instructions to README #53

Closed
ananas wants to merge 1 commit from ananas/gram:main into main
pull from: ananas/gram:main
merge into: GramEditor:main
GramEditor:main
GramEditor:test/wgpu-on-mac
GramEditor:test-ci/failing-test-mac
GramEditor:test/failing-test-mac
GramEditor:test/build-on-22-04
GramEditor:test/wgpu-present-mode-mailbox
GramEditor:v2.1
GramEditor:test/altgr-fix-again
GramEditor:test/2.0.0-rc1
GramEditor:test/linux-build
GramEditor:test/objc2
GramEditor:v1.2.1
First-time contributor
Copy link
No description provided.
Owner
Copy link

Hi!
I haven't used Arch in a long time, so I am not sure what the usual way of packaging things like gram looks like.
There is already a package for gram listed in the README, https://aur.archlinux.org/packages/gram .

Does it makes sense to have two separate packages like this? I am wondering if you can join forces with @nerdyslacker perhaps.

Hi! I haven't used Arch in a long time, so I am not sure what the usual way of packaging things like gram looks like. There is already a package for gram listed in the README, https://aur.archlinux.org/packages/gram . Does it makes sense to have two separate packages like this? I am wondering if you can join forces with @nerdyslacker perhaps.
Contributor
Copy link

Just my two cents: the existing package builds from source and it is fairly common to have two packages for such applications, one building from source and one providing the binary directly. Especially with such a heavy project, having a binary package seems desirable to me.

Just my two cents: the existing package builds from source and it is fairly common to have two packages for such applications, one building from source and one providing the binary directly. Especially with such a heavy project, having a binary package seems desirable to me.
Author
First-time contributor
Copy link

@krig wrote in #53 (comment):

Hi! I haven't used Arch in a long time, so I am not sure what the usual way of packaging things like gram looks like. There is already a package for gram listed in the README, https://aur.archlinux.org/packages/gram .

Does it makes sense to have two separate packages like this? I am wondering if you can join forces with @nerdyslacker perhaps.

like @theDoctor said, this project is heavy. Compiling it takes quite long and not everyone wants to compile it themselves. Usually on the AUR there's one build it from source and one binary version.

@krig wrote in https://codeberg.org/GramEditor/gram/pulls/53#issuecomment-11308891: > Hi! I haven't used Arch in a long time, so I am not sure what the usual way of packaging things like gram looks like. There is already a package for gram listed in the README, https://aur.archlinux.org/packages/gram . > > Does it makes sense to have two separate packages like this? I am wondering if you can join forces with @nerdyslacker perhaps. like @theDoctor said, this project is heavy. Compiling it takes quite long and not everyone wants to compile it themselves. Usually on the AUR there's one build it from source and one binary version.
Owner
Copy link

Thank you! Merged via separate PR to resolve merge conflicts.

Thank you! Merged via separate PR to resolve merge conflicts.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
GramEditor/gram!53
Reference in a new issue
GramEditor/gram
No description provided.
Delete branch "ananas/gram:main"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?