Mario Fetka 77378ef03c Merge Sabayon sabayon-distro upstream; rename overlay to sablink-distro
- profiles/repo_name: sablink-distro
- metadata/layout.conf: add thin-manifests = true
- profiles/thirdpartymirrors: add sabayon mirrors alongside sablink
- sets.conf: update to sablink-distro repository reference
- eclass/sabayon-kernel.eclass: take upstream (newer features, K_TARBALL_EXT)
- eclass/avahi.eclass: take upstream version
- profiles/package.mask: merge both comment styles
- profiles/use.local.desc: merge both USE flag descriptions

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-30 04:32:11 +02:00
2020-12-28 23:42:25 +01:00
2017-06-29 17:14:35 +02:00
2017-06-17 19:24:31 +02:00
2013-12-21 11:47:15 +01:00
2013-12-06 13:43:46 +01:00
2012-11-26 19:10:13 +01:00
2020-09-09 18:28:26 +02:00
2021-03-25 01:16:57 +01:00
2020-10-25 00:13:15 +00:00
2015-07-30 10:48:14 +02:00
2020-11-01 02:26:27 +00:00
2020-12-28 23:50:30 +01:00
2018-08-26 00:03:53 +02:00
2013-12-06 15:33:14 +01:00
2013-10-29 18:26:14 +01:00
2012-12-15 21:57:06 +01:00
2013-10-29 18:26:14 +01:00
2013-10-29 18:26:14 +01:00
2010-10-03 09:25:35 +00:00
2016-07-18 11:50:54 +02:00
2010-10-03 09:25:35 +00:00
2010-10-03 09:25:35 +00:00

Build Status Sabayon-distro overlay

This is a Gentoo overlay that contains ebuilds that are Sabayon specific and thus are not upstreamable.

If you are submitting a pull request or committing keep in mind:

  • If the ebuild/fixes you are submitting are already available in layman, the correct place is community-repositories
  • If the ebuild/fixes is generic and can be applied to Gentoo (e.g. optimizations, fixes) the correct place is sabayon overlay

Here goes:

  • ebuilds that are developed for Sabayon
  • ebuilds that are forked from Gentoo and customized for Sabayon, thus not upstreamable

Layman

This overlay is available in layman:

layman -a sabayon-distro
S
Description
No description provided
Readme 79 MiB
Languages
Shell 86.5%
C 6.5%
Roff 3.1%
Python 1.5%
Awk 1%
Other 1.4%