Overlay Name: user/wuodan Description: Personal overlay playground Owner name and e-mail: Stefan Kuhn <wuodan@hispeed.ch> SSH pubkey you’ll be pushing with: please see attachement
Created attachment 316245 [details] id_rsa.pub
Your user overlay "wuodan" 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 '${USER}' in order to make it a valid overlay. # mkdir profiles # echo "wuodan" > profiles/repo_name # git add 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.overlays.gentoo.org/user/wuodan.git # git push overlays-gentoo-org master After That ========== Online Browsing --------------- After the inital push you can browse your overlay online at: http://git.overlays.gentoo.org/gitweb/?p=user/wuodan.git;a=summary 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/wuodan/ and http://gpo.zugaina.org/Overlays/wuodan/, 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 .
(In reply to comment #2) > Just let us know that you did complete the procedure from > "The Initial Push" to get added. Thank you very much! - Initial push done. One tiny question on package-version naming: I have modified ebuilds for fluxbox, these changes will probably remain for myself only. - fluxbox-1.3.2.ebuild - fluxbox-9999.ebuild 1.3.2 is also packaged in Gentoo. Should I name it 1.3.2-r1? Then if Gentoo decides to patch their ebuild to the same name ... do I have to rename mine again? 9999 is not in Gentoo at the moment. Now if Gentoo makes a 9999.ebuild, do I have to rename mine to 9999-r1.ebuild or such? Did only commit ebuilds not in Gentoo so far. Again, thank you - Gentoo hosting user overlays is an awesome service!
(In reply to comment #3) > Thank you very much! - Initial push done. Added in layman. > One tiny question on package-version naming: > I have modified ebuilds for fluxbox, these changes will probably remain for > myself only. > - fluxbox-1.3.2.ebuild > - fluxbox-9999.ebuild > > 1.3.2 is also packaged in Gentoo. > Should I name it 1.3.2-r1? Then if Gentoo decides to patch their ebuild to > the same name ... do I have to rename mine again? As the example says, it would be good to have it as -r1 in order to avoid name overlaps. I think you can set priorities somehow in the repos, so in case of naming overlap portage will install the ebuild from the repo that you set up as priority. > 9999 is not in Gentoo at the moment. > Now if Gentoo makes a 9999.ebuild, do I have to rename mine to > 9999-r1.ebuild or such? Same for this, although live ebuilds are special and a version bump does not make sense in most cases, as people are supposed to rebuild it from time to time > Did only commit ebuilds not in Gentoo so far. > > Again, thank you - Gentoo hosting user overlays is an awesome service! You are welcome.
