| Summary: | repo/user/goris.git repository on git.gentoo.org | ||
|---|---|---|---|
| Product: | Gentoo Infrastructure | Reporter: | Norayr Mirakyan <norayr.am> |
| 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: | --- | |
| Attachments: | Public SSH key for Goris overlay. | ||
|
Description
Norayr Mirakyan
2015-08-27 11:18:18 UTC
I'll need your public SSH key (attach it or paste in a comment), and if possible a concise description I could copy-paste :). Created attachment 410472 [details]
Public SSH key for Goris overlay.
I guess "Goris overlay" will be just fine for us, if it works for you. My public SSH key is attached. Thanks again. :)
Your user overlay "goris" is almost ready.
Please read (all of) this guide to get it to work.
If you have any question we'll be here to help.
In this Guide
=============
- Terms of Service
- The Initial Push
- After That
- Online Browsing
- Getting into Layman
- Keeping your overlay healthy
Terms of Service
================
The infra team has worked out the terms of service for us. To make us host your user overlay you need to accept these terms, which I don't expect to be a problem. By pushing to the remote repository you are accepting these terms:
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Use of this service is limited to overlays containing ebuilds
and supporting files (e.g. init.d scripts, configuration
files, patches, but not distfiles) and must follow the same
guidelines as apply to the gentoo-x86 tree of Gentoo.
Any or all uses of this service and all files on this service
may be intercepted, monitored, recorded, copied, audited,
inspected, and disclosed to authorized site personnel, as well
as authorized officials of federal law enforcement agencies,
both domestic and foreign. By using this service, the user
consents to such interception, monitoring, recording, copying,
auditing, inspection, and disclosure at the discretion of
authorized site personnel. Use of this service constitutes
consent to security monitoring and testing. All activity is
logged with your host name and IP address. Unauthorized or
improper use of this service may result in civil and criminal
penalties. By continuing to use this service you indicate
your awareness of and consent to these terms and conditions of
use. -- Gentoo Linux Infrastructure Admins
CEASE USE IMMEDIATELY,
if you do not agree to the conditions stated in this warning.
*******************
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
The Initial Push
================
First, before anybody can clone from your overlay an initial push is needed.
0) If you start with an empty repository be sure to setup your identity:
# git init
# git config user.name 'first last'
# git config user.email foo@example.org
[..]
1) Once you have ebuilds in there please set profiles/repo_name to
'goris' in order to make it a valid overlay. Unless your ebuilds
do not require any eclasses or licenses, and do not depend on any
packages from Gentoo, set masters=gentoo in metadata/layout.conf
as well.
# mkdir metadata profiles
# echo "masters = gentoo" > metadata/layout.conf
# echo "goris" > profiles/repo_name
# git add metadata/layout.conf profiles/repo_name
# git commit
2) Now you are ready to push. Proposed way of doing is this:
# git remote add overlays-gentoo-org \
git+ssh://git@git.gentoo.org/repo/user/goris.git
# git push overlays-gentoo-org master
After That
==========
Online Browsing
---------------
After the initial push you can browse your overlay online at:
https://gitweb.gentoo.org/repo/user/goris.git/
Getting into Layman
-------------------
We have scripts to get hosted overlay into Layman easily: no need to write XML on your end. Just let us know that you did complete the procedure from "The Initial Push" to get added.
Once it's in the Layman registry its content will be indexed at http://gpo.zugaina.org/ and two dedicated views of your overlay will appear at http://gentoo-overlays.zugaina.org/goris/ and http://gpo.zugaina.org/Overlays/goris/, too.
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 .
Michał Górny
for the Gentoo Overlays Team
I could not push the initial commit. BTW, I wonder if repo should be "user/goris.git" instead of "repo/user/goris.git, because other user overlays have git.gentoo.org/user/name.git. Well, seems like I've succeeded in getting a couple of ebuilds and profiles/repo_name uploaded. :-) The only thing, that remains odd for me, is the difference between my repo directory and default git.gentoo.org/user/overlay-name.git pattern. Now I have completed "the Initial Push" step. Best, Norayr The repo/ namespace is intended to be used for new ebuild repositories. We may also move old repos there at some point. Now I see. :-) Do I need write another bugreport request for getting into layman or getting into layman is part of this report? Added now. I'm sorry that it took this long. Thanks again!!! |
