| Summary: | Overlay request: Piwik | ||
|---|---|---|---|
| Product: | Gentoo Infrastructure | Reporter: | Daniel Morlock <info> |
| Component: | Gentoo Overlays | Assignee: | Gentoo Overlays Project <overlays> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Daniel Morlock
2014-07-04 11:22:12 UTC
Bump. Anything missing? (In reply to Daniel Morlock from comment #0) > We would appreciate if our layman overlay get listed in the global list of > Layman Overlays: > > Name: piwik > Description: Unofficial ebuild's for Piwik > Owner: Daniel Morlock > Committers: Daniel Morlock <daniel.morlock@awesome-it.de> > > HTTP access: https://gitlab.awesome-it.de/overlays/piwik.git > > Homepage: https://gitlab.awesome-it.de/overlays/piwik > E-mail: info@awesome-it.de > > Reproducible: Always Done. Thanks for you patience. We decided to make a global overlay that contains many ebuilds that might be interested. I guess, it would make more sense, if you add this bundled overlay to Layman instead of adding the project-based overlays like e.g. for Piwik. This is our global overlay: Name: awesome Description: Awesome ebuild's Owner: Daniel Morlock Committers: Daniel Morlock <daniel.morlock@awesome-it.de> HTTP access: https://gitlab.awesome-it.de/overlays/awesome.git Homepage: https://gitlab.awesome-it.de/overlays/awesome E-mail: info@awesome-it.de If you agree, how should we proceed? Should I open new issue for adding the awesome overlay and removing the piwik overlay or is this sufficient? Basically you can just rename the Piwik overlay. Sorry for bothering you, but with the global overlay, there will be less insert-to-layman-requests =) Bump. Any progress? Done. Piwik overlay has been renamed to awesome! |
