| Summary: | add "jaervosz" to layman overlays | ||
|---|---|---|---|
| Product: | Gentoo Infrastructure | Reporter: | A. Person <tesoro302> |
| Component: | Gentoo Overlays | Assignee: | Gentoo Overlays Project <overlays> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jaervosz |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/jaervosz/portage-overlay | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
A. Person
2012-09-25 05:52:09 UTC
@Sune: - Any objections to being added? - Should the overlay be marked as official or unofficial in layman? - Please make profiles/repo_name say "jaervosz", at least something with no spaces. Thanks! No objections. I'll clean it up a bit and fix repo_name. I'll post here again when done. Most cleanup done. Please mark it as unofficial. Anything else needed? (In reply to comment #3) > Most cleanup done. Thanks! > Please mark it as unofficial. Just added as unofficial. > Anything else needed? Thanks for asking. There are two things left to wish for: - Some of the ebuilds may (or may not) be better suited for special overlay betagarden (more details below) - Command line tool "overlint" outputs a few warnings on your overlay. More on overlint below. For both of these, I take the liberty to quote from a related template below. Your overlay versus betagarden ============================== First: what is betagarden? betagarden is a special overlay that - any Gentoo developer is welcome to contribute to (you have write permissions to betagarden already) - is dedicated to ebuilds not important or good enough (i.e. of beta quality) for the main tree. Normally, a package appears in either betagarden or the main tree, but not both. Some of the ebuilds you would normally put into your developer overlay fit betagarden better. The rule of thumb is: If an ebuild (or the related upstream software) is known to be broken or quite experimental: put it in your developer overlay. All else: put it in betagarden. Thanks! Benefits include: - Other Gentoo developers can fix and bump your ebuilds for you - People do not need to keep another overlay around for just a single package they care about. That may reduce reluctance to use your ebuilds with some people. Keeping your overlay healthy ---------------------------- A few rules of thumb help to keep your overlay most useful to you and others: - If you package newer versions of software that is packaged in Gentoo already, try to get the version in Gentoo updated, too. (If there is no bump request on https://bugs.gentoo.org/ please file one and share patches you may have produced.) - If you apply custom patches make sure that you never use the very same revision that is used in Gentoo, e.g. if you use the ebuild of app-arch/bzip2-1.0.6-r3 do not call it app-arch/bzip2-1.0.6-r3 in your overlay to avoid confusion. A tool called "overlint" can support you with that process: # sudo emerge -av app-portage/overlint For a quick introduction to overlint see http://blog.hartwork.org/?p=1667 . Thank you for adding the jaervosz overlay. betagarden sound like a great idea too. |
