Bug 465400 – Please move user/TomWij to dev/TomWij

• Product: Gentoo Infrastructure
• Status: RESOLVED FIXED

[Description Tom Wijsman (TomWij) (RETIRED) 2013-04-10 14:04:07 UTC]

Can my user overlay TomWij be changed to be a dev overlay?

I plan to use it again to stage some eclass / ebuild work that would in the future be candidate to merge into the tree, rather than personal stuff; therefore it be nice that it be considered to be a dev overlay.

Thank you in advance.

[Comment 1 Sebastian Pipping 2013-05-05 15:46:59 UTC]

Done:
- Repository renamed
- Layman entry updated
  - Git source addresses
  - unofficial -> official
  - E-mail address now @gentoo.org

Please update your local remote pushing URL to

  git+ssh://[e-mail]/dev/TomWij.git

using the "git remote .." command.


Since you are a Gentoo developer by now, you do have push access to the betagarden overlay, too.  Let me add a few words on when your personal overlay is a better place than betagarden and when the other way around:


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.