[GH-ISSUE #88] Gentoo package #683

Closed
opened 2026-03-15 08:49:38 +03:00 by kerem · 10 comments
Owner

Originally created by @ku1ik on GitHub (Mar 12, 2015).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/88

The progress of packaging latest asciinema for Gentoo can be tracked here: https://bugs.gentoo.org/show_bug.cgi?id=532918

Originally created by @ku1ik on GitHub (Mar 12, 2015). Original GitHub issue: https://github.com/asciinema/asciinema/issues/88 The progress of packaging latest asciinema for Gentoo can be tracked here: https://bugs.gentoo.org/show_bug.cgi?id=532918
kerem closed this issue 2026-03-15 08:49:43 +03:00
Author
Owner

@Dr-Terrible commented on GitHub (Jun 22, 2015):

Since Gentoo developers seem reluctant to add Go packages to Portage, I have created a Portage overlay specifically for packages written in GoLang: https://github.com/Dr-Terrible/go-overlay

Despite what Michael "kensington" Palimaka said in bugs.gentoo.org, there is a straightforward way to handle the GoLang toolchain and the complexity of its dependency chain. My overlay does exactly that, and in an automated way.

All you need to do to install asciinema 1.1.0+ is to sync my overlay and then execute a simple:

emerge -av dev-go/asciinema

I'd be glad to maintain asciinema in my overlay if upstream is not willing.

p.s.: feedbacks are always welcome.

<!-- gh-comment-id:114044647 --> @Dr-Terrible commented on GitHub (Jun 22, 2015): Since Gentoo developers seem reluctant to add Go packages to _Portage_, I have created a Portage overlay specifically for packages written in GoLang: https://github.com/Dr-Terrible/go-overlay Despite what Michael "kensington" Palimaka said in bugs.gentoo.org, there is a straightforward way to handle the GoLang toolchain and the complexity of its dependency chain. My overlay does exactly that, and in an automated way. All you need to do to install asciinema 1.1.0+ is to sync my overlay and then execute a simple: <pre>emerge -av dev-go/asciinema</pre> I'd be glad to maintain _asciinema_ in my overlay if upstream is not willing. p.s.: feedbacks are always welcome.
Author
Owner

@ku1ik commented on GitHub (Jun 22, 2015):

That's great, thanks!

I have updated docs on the site to include your overlay: github.com/asciinema/asciinema.org@fd7ec57d7a
Is this the simplest way to add an overlay, or these instructions can be simpler?

<!-- gh-comment-id:114224852 --> @ku1ik commented on GitHub (Jun 22, 2015): That's great, thanks! I have updated docs on the site to include your overlay: https://github.com/asciinema/asciinema.org/commit/fd7ec57d7a8644fd4a4576cabe2ddbfb3a705981 Is this the simplest way to add an overlay, or these instructions can be simpler?
Author
Owner

@Dr-Terrible commented on GitHub (Jun 23, 2015):

That's great, thanks!

You're welcome.

Is this the simplest way to add an overlay, or these instructions can be simpler?

Yeah, those instructions are the simplest way for adding an external overlay. Unfortunately there aren't shortcuts for these kind of tasks in Gentoo: https://wiki.gentoo.org/wiki/Project:Overlays/User_Guide#Getting_Started_With_Overlays

The only way to bypass wget (and the manual regeneration of the local cache of Layman) is by adding my overlay to https://overlays.gentoo.org . That way the instructions will boil down to a mere:

layman -a go-overlay
emerge -av asciinema

I have officially made a request for the inclusion of my overlay into Layman's list of repositories (unfortunately, some considerable delay should be expected from upstream): https://bugs.gentoo.org/552918

When my request will be fulfilled, you can safely update the docs with the two aforementioned commands.

<!-- gh-comment-id:114425261 --> @Dr-Terrible commented on GitHub (Jun 23, 2015): > That's great, thanks! You're welcome. > Is this the simplest way to add an overlay, or these instructions can be simpler? Yeah, those instructions are the simplest way for adding an external overlay. Unfortunately there aren't shortcuts for these kind of tasks in _Gentoo_: https://wiki.gentoo.org/wiki/Project:Overlays/User_Guide#Getting_Started_With_Overlays The only way to bypass _wget_ (and the manual regeneration of the local cache of _Layman_) is by adding my overlay to https://overlays.gentoo.org . That way the instructions will boil down to a mere: <pre>layman -a go-overlay emerge -av asciinema</pre> I have officially made a request for the inclusion of my overlay into _Layman_'s list of repositories (unfortunately, some considerable delay should be expected from upstream): https://bugs.gentoo.org/552918 When my request will be fulfilled, you can safely update the docs with the two aforementioned commands.
Author
Owner

@ku1ik commented on GitHub (Jun 23, 2015):

Sounds good. Can you let me know when this happens so I can update the docs?

<!-- gh-comment-id:114428416 --> @ku1ik commented on GitHub (Jun 23, 2015): Sounds good. Can you let me know when this happens so I can update the docs?
Author
Owner

@Dr-Terrible commented on GitHub (Jun 23, 2015):

Can you let me know when this happens so I can update the docs?

Sure. As soon as my overlay has been added to Layman's repositories.xml, I'll post here a note.

<!-- gh-comment-id:114451774 --> @Dr-Terrible commented on GitHub (Jun 23, 2015): > Can you let me know when this happens so I can update the docs? Sure. As soon as my overlay has been added to Layman's repositories.xml, I'll post here a note.
Author
Owner

@Dr-Terrible commented on GitHub (Jun 25, 2015):

Done! The overlay has been added to http://overlay.gentoo.org. @sickill feel free to update asciinema's documentation.

<!-- gh-comment-id:115214955 --> @Dr-Terrible commented on GitHub (Jun 25, 2015): Done! The overlay has been added to http://overlay.gentoo.org. @sickill feel free to update asciinema's documentation.
Author
Owner

@ku1ik commented on GitHub (Jun 25, 2015):

@Dr-Terrible awesome.

Should it be now emerge -av asciinema or emerge -av dev-go/asciinema?

<!-- gh-comment-id:115258038 --> @ku1ik commented on GitHub (Jun 25, 2015): @Dr-Terrible awesome. Should it be now `emerge -av asciinema` or `emerge -av dev-go/asciinema`?
Author
Owner

@Dr-Terrible commented on GitHub (Jun 26, 2015):

I kept the original nomenclature from Portage's tree to avoid points of friction / confusion for the final users, so (sudo) emerge -av asciinema or (sudo) emerge -av app-misc/asciinema are both perfectly fine.

This way, asciinema package from my overlay will act as a standard and completely transparent update (from 0.9.8 to 1.1.1+) for all the Gentoo users.

<!-- gh-comment-id:115587375 --> @Dr-Terrible commented on GitHub (Jun 26, 2015): I kept the original nomenclature from _Portage_'s tree to avoid points of friction / confusion for the final users, so `(sudo) emerge -av asciinema` or `(sudo) emerge -av app-misc/asciinema` are both perfectly fine. This way, _asciinema_ package from my overlay will act as a standard and completely transparent update (from 0.9.8 to 1.1.1+) for all the Gentoo users.
Author
Owner

@ku1ik commented on GitHub (Jun 26, 2015):

Nice. Thanks for your work!

<!-- gh-comment-id:115589716 --> @ku1ik commented on GitHub (Jun 26, 2015): Nice. Thanks for your work!
Author
Owner

@Dr-Terrible commented on GitHub (Jun 26, 2015):

You're welcome.
I’m glad I was able to help. :)

<!-- gh-comment-id:115701902 --> @Dr-Terrible commented on GitHub (Jun 26, 2015): You're welcome. I’m glad I was able to help. :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
starred/asciinema#683
No description provided.