Core Developer Reference - Revision history

Golodhrim: /* Funtoo portage tree */ adding link to Git Guide

2011-04-29T18:48:52Z

‎Funtoo portage tree: adding link to Git Guide

404 Error: /* Update the additions/forks pages in the wiki */

2011-04-18T20:07:16Z

‎Update the additions/forks pages in the wiki

404 Error: /* Update the additions/forks pages in the wiki */

2011-04-18T19:27:53Z

‎Update the additions/forks pages in the wiki

404 Error: /* Things to do after pushing a package (update or new) - IMPORTANT */

2011-04-18T19:23:18Z

‎Things to do after pushing a package (update or new) - IMPORTANT

Golodhrim: /* Funtoo portage tree */

2011-04-18T16:20:34Z

‎Funtoo portage tree

D2 racing: /* Core developers */

2011-04-18T15:07:11Z

‎Core developers

D2 racing: Typo

2011-04-18T15:06:55Z

Typo

404 Error: /* Committing your changes on funtoo-overlay/profile/package.mask */

2011-04-15T21:06:25Z

‎Committing your changes on funtoo-overlay/profile/package.mask

404 Error: rewording

2011-04-15T21:02:29Z

rewording

404 Error: /* Committing your changes on funtoo-overlay/profile/package.mask */

2011-04-15T21:00:27Z

‎Committing your changes on funtoo-overlay/profile/package.mask

@@ Line 17: / Line 17: @@
 ** Bar overlay (404 error)
 ** Golodhrim overlay (golodhrim)
 When a new core developer or contributor want to share his ebuild repository, he must:

@@ Line 161: / Line 161: @@
 == Update the additions/forks pages in the wiki ==
 Depending on what you did, please update the following pages:
-* [[Forked_Ebuilds]] if you have forked an '''existing''' Gentoo package
+* [[Forked_Ebuilds]] if you have forked an '''existing''' Gentoo package (giving a new revision)
-* [[Specific_Funtoo_Ebuilds]] if you have introduced '''a new package''' in Funtoo
+* [[Specific_Funtoo_Ebuilds]] if you have introduced '''a totally new package''' in Funtoo (not a revision of an existing Gentoo/Funtoo package)
 [[Category:Internals]]

@@ Line 160: / Line 160: @@
 == Update the additions/forks pages in the wiki ==
-Depending on what you did, please update:
+Depending on what you did, please update the following pages:
-* [[Forked_Ebuilds]] if you have forked an existing Gentoo package
+* [[Forked_Ebuilds]] if you have forked an '''existing''' Gentoo package
-* [[Specific_Funtoo_Ebuilds]] if you have introduced a new package in Funtoo
+* [[Specific_Funtoo_Ebuilds]] if you have introduced '''a new package''' in Funtoo
 [[Category:Internals]]

@@ Line 151: / Line 151: @@
 = Things to do after pushing a package (update or new) - IMPORTANT =
 '''The following is not optional so pay attention''': once your bits have been pushed on GitHub, you have to post a notice about what you have updated/added to the Funtoo tree on all of the following Funtoo communication channels:
@@ Line 157: / Line 158: @@
 The reason is simple: some of the Funtoo users use the mailing list and some others prefer to use the Funtoo forums and both categories must be reached.
 [[Category:Internals]]

@@ Line 13: / Line 13: @@
 * Merges with the Multimedia overlay (only one package here -> media-video/mplayer-uau)
 * Merges with the overlays maintained by several Funtoo developpers:
-** Tarsius overlay (tarsius)
+** Tarsius overlay (tarsius/Funtoo Core Team)
 ** Foo overlay (slashbeast)
 ** Bar overlay (404 error)
 When a new core developer or contributor want to share his ebuild repository, he must:

@@ Line 3: / Line 3: @@
 = Core developers =
-A Funtoo core developer is a memeber of the [[Core Team]] who help in the maintenance/evolution of Funtoo Linux.
+A Funtoo core developer is a member of the [[Core Team]] who help in the maintenance/evolution of Funtoo Linux.
 = Funtoo portage tree =

@@ Line 146: / Line 146: @@
 # You commit and push your changes in profiles/packages.mask to mask
-This could lead to a catastrophic failure for Funtoo users the next time they will resync their portage tree if your package breaks for various reasons or if the deployed software has severe issues that you had not been able to detect on your side.
+'''Not respecting this order could lead to ''catastrophic'' consequences for Funtoo users the next time they will resync their portage tree''' if your package breaks for various reasons or if the deployed software has severe issues that you had not been able to detect on your side.
 = Things to do after pushing a package (update or new) - IMPORTANT =

@@ Line 135: / Line 135: @@
 == Committing your changes on funtoo-overlay/profile/package.mask ==
-A '''highly recommended''' way to commit your changes is the following order:
+A '''highly recommended''' way to commit your changes is to proceed in the following order:
 # Commit and push the changes brought in profiles/packages.mask
 # Commit and push the changes brought in the package tree (in your overlay and/or the funtoo-overlay in itself).
-Why? Simple: remember that the Funtoo portage tree is automatically refreshed every 12 hours and this refresh of merging several Funtoo developers repositories on GitHub, the Funtoo overlay master copy (also located on GitHub) and a snapshot of the Gentoo portage tree. At the time you commit, it is not impossible that  the refreshment process and you are acting in a concurrent way. So imagine the following scenario:
+Why? Simple: remember that the Funtoo portage tree is automatically refreshed every 12 hours and this refresh of merging several Funtoo developers repositories on GitHub, the Funtoo overlay master copy (also located on GitHub) and a snapshot of the Gentoo portage tree. At the time you commit, it is not impossible that  the refreshment process and you are acting in a concurrent way and the following scenario could occur:
-# You have updated some Funtoo core packages (or worse a Funtoo critical package) and you commit and push the changes brought either in the Funtoo overlay either in your local repository on GitHub
+# You have updated some Funtoo core packages (or, worse, a Funtoo critical package) and you commit and push the changes brought either in the Funtoo overlay either in your local repository on GitHub
 # The Funtoo tree refreshment process starts and grab the place where your updated package resides and the profiles/packages.mask directory in the Funtoo overlay
 # You commit and push your changes in profiles/packages.mask to mask