[gentoo-dev] Re: [PATCH 0/5] RFC: Patches for wxwidgets.eclass

[Ryan Hill]

On Wed, 3 Feb 2016 17:07:48 -0800
Daniel Campbell  wrote:

> I see nothing wrong with discussing changes to parts of the tree that
> will affect other developers. Bugzilla is nice and all, but imo it's
> more of an AND thing instead of an OR thing. If the bug is already
> present, I see no real reason not to have a thread about it on g-dev.
> It keeps unrelated developers in the loop, as well, in the event that
> they come across weird eclass behavior or take on a project using a
> given eclass.
> 
> I guess if eclass discussion is a problem, one could always add a rule
> to whatever they use to filter their mail.

I had thought that this got sent to gentoo-dev but not to wxwidgets, and I got
the impression that patches were being proposed for our eclass only here, where
I would have missed them (I don't read this list).  I didn't notice until today
we were CC'd.  I didn't see these come through on that alias, but I think my
mailer is eating messages again.

Sorry for the noise.


-- 


pgp3wQ8xwjPzl.pgp
Description: OpenPGP digital signature

Re: [gentoo-dev] [PATCH v3 05/21] ebuild-writing/misc-files: replace the code for cvs commit with git #558642

[Brian Dolbec]

On Wed,  3 Feb 2016 19:57:33 -0500
gokt...@binghamton.edu wrote:

> From: Gokturk Yuksek 
> 
> Replace "cvs commit" with the equivalent "git add && git commit"
> version.
> 
> Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
> Signed-off-by: Gokturk Yuksek 
> ---
>  ebuild-writing/misc-files/metadata/text.xml | 16 +++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/ebuild-writing/misc-files/metadata/text.xml
> b/ebuild-writing/misc-files/metadata/text.xml index e506b1c..2de3cf5
> 100644 --- a/ebuild-writing/misc-files/metadata/text.xml
> +++ b/ebuild-writing/misc-files/metadata/text.xml
> @@ -532,7 +532,21 @@ is currently:
>  
>  xmllint --noout --valid metadata.xml
>  glep31check metadata.xml
> -cvs commit -m "Adding category metadata.xml for my-category"
> metadata.xml +git add metadata.xml
> +git commit --gpg-sign
>

This should be repoman commit still, not git commit

 +
> +
> +
> +The commit message should be formatted properly.
> +A sample commit is shown below:
> +
> +
> +
> +commit db359439bcd52f5a7f20d2332ab62feb16657504
> +Author: Alexis Ballier 
> +Date:   Tue Sep 22 10:47:49 2015 +0200
> +
> +  dev-ros: Add metadata.xml for the category.
>  
>  
>  



-- 
Brian Dolbec 

Re: [gentoo-dev] [PATCH v3 00/21] devmanual: update the docs for post git-migration

[Daniel Campbell]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/03/2016 05:49 PM, Göktürk Yüksek wrote:
> Daniel Campbell:
>> On 02/03/2016 04:57 PM, gokt...@binghamton.edu wrote:
>>> From: Gokturk Yuksek 
> 
>>> Hi,
> 
>> [...]
> 
>> This isn't related to what you're doing but I felt it was a good
>>  place to ask:
> 
>> How are you and other developers creating these series of
>> e-mails? It seems really handy and I'd like to know what it is,
>> in the event that I need to do the same.
> 
> 
> 
> Here's how I do it: Make your commits on a separate branch as if
> you'd push them directly to the repo. Use 'git format-patch' to
> generate patch files and use 'git send-email' to send them. You can
> skip format-patch and just use send-email but for a changeset of 21
> commits I'd like to take another look.
> 
> git format-patch --stat --summary -o bug558642_v3/ -n -v3 
> --cover-letter master..devmanual-git-migration-v3
> 
> Creates the patches. '--cover-letter' creates a special patch file 
> that requires editing which becomes the first email in the series, 
> which is the one you replied to.
> 
> Once satisfied, I sent it with:
> 
> git send-email *
> 
> Keep in mind that git will CC authors of the patches and yourself
> to the email. So you may have to adjust those.
> 
> Don't forget to edit your .gitconfig and set proper SMTP options
> in the [sendemail] section.
> 
> 
Awesome; between the manpage and your example this is a great primer!
Thanks a lot for explaining your workflow. I'm sure it's useful to
more than just myself.


- -- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWsq8HAAoJEAEkDpRQOeFw+HUP/2QEbZNPNmrZGM2DGVzAIY+/
wQvGpIq8IO6SQ6pQH8FLFeTb17Y2x+SB04rYqv3bpbOV/GjSPwAomObLBa4GUU74
QTnZ7p4ZfMxisiZd5IfFPNMuY2YTpT2TfRez1TPxdty+4w9aE/MjYNvk/pTqhc4D
fVI8NdMixP8obDozXqvqKSV2uh0smE82aFleAN7yQ9pEplV/282UqdcFRIQs6iXX
7gCxZvTbaXTuvukda8D8uABrZSvZhORjZ4TmnZfEHQcih9byF9smk/Ao1uNbTXG2
iJRkvDld0wfkar6o8zoX9tEjwwpVXfSSjnDcEZSYYO90Q3aY3HNWttcgRilD4HXA
wd57r5eDZUM82IY70oGhHPDEeW+lXoKgp3B8LYQCdGOJRLgSPC6F9WGvAvf/qK8h
ULg1WPbjMudWU1gnzNxaX2f3WT6+RoyZccpUMKNg/Ku2glG/6ZVPbkpm8Z4Uo/yd
iuhpCcs3HVHWvZS7ggJk7FysxlBwH5Zd4+88USo/HujUfjkdvJgZ7COAV8DTikAg
3n2U+MFIUDwjfp014MgKKTdTt0Cj2n87LPCeQN+hEeGPOfz6jAr2TBrRGdyCEHBi
aYHbny9tFs3na4HJhBquE5Esm159T+RY7Ff7br1zzIu8hhNNIlCsN8xxRku9jCsx
wT5s3gCj/o4ElV+EumhX
=BZ+P
-END PGP SIGNATURE-

Re: [gentoo-dev] [PATCH v3 00/21] devmanual: update the docs for post git-migration

[Göktürk Yüksek]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Daniel Campbell:
> On 02/03/2016 04:57 PM, gokt...@binghamton.edu wrote:
>> From: Gokturk Yuksek 
> 
>> Hi,
> 
> [...]
> 
> This isn't related to what you're doing but I felt it was a good 
> place to ask:
> 
> How are you and other developers creating these series of e-mails? 
> It seems really handy and I'd like to know what it is, in the
> event that I need to do the same.
> 
> 

Here's how I do it: Make your commits on a separate branch as if you'd
push them directly to the repo. Use 'git format-patch' to generate
patch files and use 'git send-email' to send them. You can skip
format-patch and just use send-email but for a changeset of 21 commits
I'd like to take another look.

git format-patch --stat --summary -o bug558642_v3/ -n -v3
- --cover-letter master..devmanual-git-migration-v3

Creates the patches. '--cover-letter' creates a special patch file
that requires editing which becomes the first email in the series,
which is the one you replied to.

Once satisfied, I sent it with:

git send-email *

Keep in mind that git will CC authors of the patches and yourself to
the email. So you may have to adjust those.

Don't forget to edit your .gitconfig and set proper SMTP options in
the [sendemail] section.

- --
gokturk
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJWsq3CAAoJEIT4AuXAiM4zuIEH/AvY3LYbcPMONlA5KuXTYTBG
8AtgqynEmQ0Qt1XujbC8W2bsKRMiUi8Xbtttnm/urfVCzCDKVQrzIkIA4x4kqIxA
HKYgLuqE2zLxfLrbJkB0W3F1ogNOt1fuxzR9HSlasgqOSh13tpexINvI77iC4U0T
7ZlUeRv5R7AqvObEZO+2hY3JkHCELgD4lwRkNwjzqNVqJLJOVUev3wXid38GBPf2
qQUEUdZw5XuM5ygFM0r5ZgP2X8HEs5FfB9ouAHGuw7d/Kr+R3L+vH1v5g4+D+n1f
iink8nR2LMrcBRiQ4/tbXyBgBiu/jZeG5UTJfQte3jyOuP4kf65SFADW+3B4+cc=
=46ba
-END PGP SIGNATURE-

Re: [gentoo-dev] [PATCH v3 00/21] devmanual: update the docs for post git-migration

[Daniel Campbell]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/03/2016 05:15 PM, NP-Hardass wrote:
> On 02/03/2016 08:10 PM, Daniel Campbell wrote:
>> On 02/03/2016 04:57 PM, gokt...@binghamton.edu wrote:
>>> From: Gokturk Yuksek 
> 
>>> Hi,
> 
>>> This is the third iteration of the patch series that attempts
>>> to update the devmanual for the git migration.
> 
>>> The updates included in the third revision are: - Added a new 
>>> subsection called "Git Commit Message Format" based on the 
>>> commit message format included in the Gentoo Git Workflow wiki 
>>> and the feedback provided on this mailing list. - Based on the 
>>> discussion wrt how well git deals with compressed patches,
>>> I've decided to remove "because git does not play well with
>>> binary files".  It's a policy we have been following for years 
>>> irrespective of how git deals with them. - Rewrote the
>>> subsection on "Removing a package" so it does not use 'git
>>> commit -m'. Rewrote the example and added the corresponding
>>> commit message as an example. - The subsection "User-submitted
>>> Ebuilds" is modified to mention the use of git style tags in
>>> commit messages and a reference to the commit message format
>>> policy section has been added.
> 
>>> You can review the changes on Github for your own convenience:
>>>  
>>> https://github.com/gktrk/devmanual.gentoo.org/compare/master...gktrk:
>
>>> 
devmanual-git-migration-v3
> 
>>> If you want to see the diff between v2 and v3, you can clone
>>> the Github repo and check the diff between the branches 
>>> "devmanual-git-migration-v2" and "devmanual-git-migration-v3".
> 
>>> The HTML version of the devmanual with the proposed changes
>>> can be found at: http://devmanual.qui-gon.org/
> 
>>> Gokturk Yuksek (19): general-concepts/manifest: drop the use of
>>>  "CVS keyword expansion" #558642 general-concepts/mirrors: 
>>> substitute "CVS" with "the git tree" #558642 
>>> general-concepts/tree: substitute "CVS" with "git" #558642 
>>> general-concepts/tree: replace the mention of ChangeLog
>>> #558642 ebuild-writing/misc-files: replace the code for cvs
>>> commit with git #558642 ebuild-writing/user-submitted: do not
>>> put user information in ChangeLog #558642 
>>> appendices/editor-configuration/emacs: remove the CVS related 
>>> setting #558642 ebuild-maintenance: rewrite the text on adding 
>>> binary files to the tree #558642 ebuild-maintenance: rewrite
>>> the subsection on commit policy for git #558642
>>> ebuild-maintenance: rewrite the subsection on upgrading ebuilds
>>> for git #558642 ebuild-maintenance: rewrite the subsection on
>>> moving ebuilds for git #558642 ebuild-maintenance: rewrite the
>>> subsection on removing ebuilds for git #558642
>>> ebuild-maintenance: rewrite the subsection on removing packages
>>> for git #558642 ebuild-maintenance: replace "cvs commit" with
>>> "git commit" #558642 general-concepts/git-to-rsync/diagram:
>>> update the description for git #558642 
>>> general-concepts/git-to-rsync/diagram: update the description
>>> for git #558642 general-concepts/tree: remove the reference to
>>> the ChangeLog #485314 ebuid-maintenance: add a new section
>>> called "Git Commit Message Format" #558642 
>>> ebuild-writing/user-submitted: mention git style tags in commit
>>>  messages #558642
> 
>>> Michael Orlitzky (2): ebuild-writing/misc-files: remove 
>>> ChangeLog section #485314 tools-reference: remove the
>>> echangelog page #485314
> 
>>> appendices/editor-configuration/emacs/text.xml |   4 +- 
>>> ebuild-maintenance/text.xml| 281 
>>> +++-- 
>>> ebuild-writing/common-mistakes/text.xml |   2 +- 
>>> ebuild-writing/misc-files/changelog/text.xml   | 111
>>> -- ebuild-writing/misc-files/metadata/text.xml|  16
>>> +- ebuild-writing/misc-files/text.xml |   1 - 
>>> ebuild-writing/user-submitted/text.xml |  14 +- 
>>> general-concepts/git-to-rsync/diagram.svg  |   2 +- 
>>> general-concepts/manifest/text.xml |   4 +- 
>>> general-concepts/mirrors/diagram.svg   |   2 +- 
>>> general-concepts/mirrors/text.xml  |   2 +- 
>>> general-concepts/tree/text.xml |   5 +- 
>>> tools-reference/echangelog/text.xml|  32 --- 
>>> tools-reference/text.xml   |   1 - 14 files
>>>  changed, 247 insertions(+), 230 deletions(-) delete mode
>>> 100644 ebuild-writing/misc-files/changelog/text.xml delete mode
>>> 100644 tools-reference/echangelog/text.xml
> 
> 
>> This isn't related to what you're doing but I felt it was a good 
>> place to ask:
> 
>> How are you and other developers creating these series of
>> e-mails? It seems really handy and I'd like to know what it is,
>> in the event that I need to do the same.
> 
> 
> 
> git send-email
> 
> 
Cool, thanks. I knew git had e-mail features but hadn't trawled
through the manpage to see what they were all about. I didn't know it
was so easy! :)


- -- 
Daniel Campbell - Gento

Re: [gentoo-dev] [PATCH v3 00/21] devmanual: update the docs for post git-migration

[NP-Hardass]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/03/2016 08:10 PM, Daniel Campbell wrote:
> On 02/03/2016 04:57 PM, gokt...@binghamton.edu wrote:
>> From: Gokturk Yuksek 
> 
>> Hi,
> 
>> This is the third iteration of the patch series that attempts to
>>  update the devmanual for the git migration.
> 
>> The updates included in the third revision are: - Added a new 
>> subsection called "Git Commit Message Format" based on the
>> commit message format included in the Gentoo Git Workflow wiki
>> and the feedback provided on this mailing list. - Based on the
>> discussion wrt how well git deals with compressed patches, I've
>> decided to remove "because git does not play well with binary
>> files".  It's a policy we have been following for years
>> irrespective of how git deals with them. - Rewrote the subsection
>> on "Removing a package" so it does not use 'git commit -m'.
>> Rewrote the example and added the corresponding commit message as
>> an example. - The subsection "User-submitted Ebuilds" is modified
>> to mention the use of git style tags in commit messages and a
>> reference to the commit message format policy section has been
>> added.
> 
>> You can review the changes on Github for your own convenience: 
>> https://github.com/gktrk/devmanual.gentoo.org/compare/master...gktrk:
devmanual-git-migration-v3
>
>>  If you want to see the diff between v2 and v3, you can clone the
>>  Github repo and check the diff between the branches 
>> "devmanual-git-migration-v2" and "devmanual-git-migration-v3".
> 
>> The HTML version of the devmanual with the proposed changes can
>> be found at: http://devmanual.qui-gon.org/
> 
>> Gokturk Yuksek (19): general-concepts/manifest: drop the use of 
>> "CVS keyword expansion" #558642 general-concepts/mirrors: 
>> substitute "CVS" with "the git tree" #558642
>> general-concepts/tree: substitute "CVS" with "git" #558642
>> general-concepts/tree: replace the mention of ChangeLog #558642
>> ebuild-writing/misc-files: replace the code for cvs commit with
>> git #558642 ebuild-writing/user-submitted: do not put user
>> information in ChangeLog #558642
>> appendices/editor-configuration/emacs: remove the CVS related
>> setting #558642 ebuild-maintenance: rewrite the text on adding
>> binary files to the tree #558642 ebuild-maintenance: rewrite the
>> subsection on commit policy for git #558642 ebuild-maintenance: 
>> rewrite the subsection on upgrading ebuilds for git #558642 
>> ebuild-maintenance: rewrite the subsection on moving ebuilds for 
>> git #558642 ebuild-maintenance: rewrite the subsection on
>> removing ebuilds for git #558642 ebuild-maintenance: rewrite the
>> subsection on removing packages for git #558642
>> ebuild-maintenance: replace "cvs commit" with "git commit"
>> #558642 general-concepts/git-to-rsync/diagram: update the
>> description for git #558642
>> general-concepts/git-to-rsync/diagram: update the description for
>> git #558642 general-concepts/tree: remove the reference to the
>> ChangeLog #485314 ebuid-maintenance: add a new section called
>> "Git Commit Message Format" #558642 
>> ebuild-writing/user-submitted: mention git style tags in commit 
>> messages #558642
> 
>> Michael Orlitzky (2): ebuild-writing/misc-files: remove
>> ChangeLog section #485314 tools-reference: remove the echangelog
>> page #485314
> 
>> appendices/editor-configuration/emacs/text.xml |   4 +- 
>> ebuild-maintenance/text.xml| 281 
>> +++--
>> ebuild-writing/common-mistakes/text.xml |   2 +-
>> ebuild-writing/misc-files/changelog/text.xml   | 111 --
>> ebuild-writing/misc-files/metadata/text.xml|  16 +- 
>> ebuild-writing/misc-files/text.xml |   1 - 
>> ebuild-writing/user-submitted/text.xml |  14 +- 
>> general-concepts/git-to-rsync/diagram.svg  |   2 +- 
>> general-concepts/manifest/text.xml |   4 +- 
>> general-concepts/mirrors/diagram.svg   |   2 +- 
>> general-concepts/mirrors/text.xml  |   2 +- 
>> general-concepts/tree/text.xml |   5 +- 
>> tools-reference/echangelog/text.xml|  32 --- 
>> tools-reference/text.xml   |   1 - 14 files 
>> changed, 247 insertions(+), 230 deletions(-) delete mode 100644 
>> ebuild-writing/misc-files/changelog/text.xml delete mode 100644 
>> tools-reference/echangelog/text.xml
> 
> 
> This isn't related to what you're doing but I felt it was a good
> place to ask:
> 
> How are you and other developers creating these series of e-mails?
> It seems really handy and I'd like to know what it is, in the event
> that I need to do the same.
> 
> 

git send-email

- -- 
NP-Hardass
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWsqZBAAoJEBzZQR2yrxj7+KIP/A8F4Q043VPLxpv2oWJJrrtq
LCRHke5l1V37Ox9gPpvGFs5WLV/CdsXMsisOb3wAPB994FM1NXwuvIbpI6C/FUFY
BG1exENtD7TwYwNvoXcZG+YAd150EKcqEqKPsNQqKxMy6Pl+W3opNBY97J2b4C+R
LOedWHPZtMUr/NuutBso2Av0kZQQlZNIiMThCDzOWiju6gD5uhzTxJ3i0zzxzZRt
vCey

Re: [gentoo-dev] [PATCH v3 00/21] devmanual: update the docs for post git-migration

[Daniel Campbell]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/03/2016 04:57 PM, gokt...@binghamton.edu wrote:
> From: Gokturk Yuksek 
> 
> Hi,
> 
> This is the third iteration of the patch series that attempts to 
> update the devmanual for the git migration.
> 
> The updates included in the third revision are: - Added a new
> subsection called "Git Commit Message Format" based on the commit
> message format included in the Gentoo Git Workflow wiki and the
> feedback provided on this mailing list. - Based on the discussion
> wrt how well git deals with compressed patches, I've decided to
> remove "because git does not play well with binary files".  It's a
> policy we have been following for years irrespective of how git
> deals with them. - Rewrote the subsection on "Removing a package"
> so it does not use 'git commit -m'. Rewrote the example and added
> the corresponding commit message as an example. - The subsection
> "User-submitted Ebuilds" is modified to mention the use of git
> style tags in commit messages and a reference to the commit message
> format policy section has been added.
> 
> You can review the changes on Github for your own convenience: 
> https://github.com/gktrk/devmanual.gentoo.org/compare/master...gktrk:devmanual-git-migration-v3
>
>  If you want to see the diff between v2 and v3, you can clone the 
> Github repo and check the diff between the branches 
> "devmanual-git-migration-v2" and "devmanual-git-migration-v3".
> 
> The HTML version of the devmanual with the proposed changes can be
> found at: http://devmanual.qui-gon.org/
> 
> Gokturk Yuksek (19): general-concepts/manifest: drop the use of
> "CVS keyword expansion" #558642 general-concepts/mirrors:
> substitute "CVS" with "the git tree" #558642 general-concepts/tree:
> substitute "CVS" with "git" #558642 general-concepts/tree: replace
> the mention of ChangeLog #558642 ebuild-writing/misc-files: replace
> the code for cvs commit with git #558642 
> ebuild-writing/user-submitted: do not put user information in 
> ChangeLog #558642 appendices/editor-configuration/emacs: remove the
> CVS related setting #558642 ebuild-maintenance: rewrite the text on
> adding binary files to the tree #558642 ebuild-maintenance: rewrite
> the subsection on commit policy for git #558642 ebuild-maintenance:
> rewrite the subsection on upgrading ebuilds for git #558642 
> ebuild-maintenance: rewrite the subsection on moving ebuilds for
> git #558642 ebuild-maintenance: rewrite the subsection on removing
> ebuilds for git #558642 ebuild-maintenance: rewrite the subsection
> on removing packages for git #558642 ebuild-maintenance: replace
> "cvs commit" with "git commit" #558642 
> general-concepts/git-to-rsync/diagram: update the description for
> git #558642 general-concepts/git-to-rsync/diagram: update the
> description for git #558642 general-concepts/tree: remove the
> reference to the ChangeLog #485314 ebuid-maintenance: add a new
> section called "Git Commit Message Format" #558642 
> ebuild-writing/user-submitted: mention git style tags in commit 
> messages #558642
> 
> Michael Orlitzky (2): ebuild-writing/misc-files: remove ChangeLog
> section #485314 tools-reference: remove the echangelog page
> #485314
> 
> appendices/editor-configuration/emacs/text.xml |   4 +- 
> ebuild-maintenance/text.xml| 281
> +++-- ebuild-writing/common-mistakes/text.xml
> |   2 +- ebuild-writing/misc-files/changelog/text.xml   | 111
> -- ebuild-writing/misc-files/metadata/text.xml|  16 +- 
> ebuild-writing/misc-files/text.xml |   1 - 
> ebuild-writing/user-submitted/text.xml |  14 +- 
> general-concepts/git-to-rsync/diagram.svg  |   2 +- 
> general-concepts/manifest/text.xml |   4 +- 
> general-concepts/mirrors/diagram.svg   |   2 +- 
> general-concepts/mirrors/text.xml  |   2 +- 
> general-concepts/tree/text.xml |   5 +- 
> tools-reference/echangelog/text.xml|  32 --- 
> tools-reference/text.xml   |   1 - 14 files
> changed, 247 insertions(+), 230 deletions(-) delete mode 100644
> ebuild-writing/misc-files/changelog/text.xml delete mode 100644
> tools-reference/echangelog/text.xml
> 

This isn't related to what you're doing but I felt it was a good place
to ask:

How are you and other developers creating these series of e-mails? It
seems really handy and I'd like to know what it is, in the event that
I need to do the same.

- -- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWsqUGAAoJEAEkDpRQOeFw1tcQANTfi+BFhZJDk2AY5N1Cy5jW
tMdVsnaFLR/up2MAQx53TPhJ9k4BKIpl9+fFmaY5iFs1KshRtYQ3fNWzs/oO2oby
X1lKWdO8y8QqGPUY9xkiq5LxujfcI+ZcGBhTN1Ir6CZJMLmrxGlytCGqs8b/2beU
sGe4Puzjvly1CwyfROUzlksJpP/+0z+jrJIHmYp2gwPTKnpIuQ5hdx3l6N0kP/hF
diizpptajir3HYDgz6Fdge8HHmlGqD8t62sSnbCyIy9CR28T5

Re: [gentoo-dev] Re: [PATCH 0/5] RFC: Patches for wxwidgets.eclass

[Daniel Campbell]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/02/2016 02:36 PM, Ryan Hill wrote:
> On Mon,  1 Feb 2016 12:08:28 +0100 Justin Lecher 
> wrote:
> 
>> while tracking down the following error when running "egencache"
>> 
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command
>> not found GENTOO.GIT//eclass/wxwidgets.eclass: line 84:
>> get_libdir: command not found 
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command
>> not found GENTOO.GIT//eclass/wxwidgets.eclass: line 84:
>> get_libdir: command not found 
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command
>> not found GENTOO.GIT//eclass/wxwidgets.eclass: line 84:
>> get_libdir: command not found 
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command
>> not found GENTOO.GIT//eclass/wxwidgets.eclass: line 84:
>> get_libdir: command not found 
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command
>> not found
>> 
>> I found that the global scope get_libdir() usage of the
>> wxwidgets.eclass doens't work on EAPI=6. The following patches
>> correct some minor things and block EAPI=6 for now until the
>> eclass is ready.
>> 
>> Justin Lecher (5): wxwidgets.eclass: Update Copyright year 
>> wxwidgets.eclass: Fix whitespaces wxwidgets.eclass: unset
>> unneeded variables in global scope after usage wxwidgets.eclass:
>> Only inherit eclass ones wxwidgets.eclass: Add EAPI support
>> 
>> eclass/wxwidgets.eclass | 33 - 1
>> file changed, 24 insertions(+), 9 deletions(-)
>> 
> 
> 1. I don't think most of this is necessary but go ahead I guess. 2.
> When did we start posting every @&#$! eclass change to g-dev?  File
> a bug like a normal person.  (There's already one open you could
> have used)
> 
> 

I see nothing wrong with discussing changes to parts of the tree that
will affect other developers. Bugzilla is nice and all, but imo it's
more of an AND thing instead of an OR thing. If the bug is already
present, I see no real reason not to have a thread about it on g-dev.
It keeps unrelated developers in the loop, as well, in the event that
they come across weird eclass behavior or take on a project using a
given eclass.

I guess if eclass discussion is a problem, one could always add a rule
to whatever they use to filter their mail.

- -- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWsqRfAAoJEAEkDpRQOeFwMNEQAJTu8qR9PRV0yWOJpiUdNYXM
bdshcE17w41+xXSdDK+rhWxdQeZwG5fzxzqwtvzNr8lYtKPuTOaKRNV/KxjhBMH8
tiwIfggw0RfnKnlysQPXMB6YDrbkYAYZmRIObZBF9ZBhLqkod+HW2Ek0gLUfC1jP
3HIU6ymexHc+AGehw/L6FzQPGnv7SSDcTFqU8XI5HZZjT4M4xGdU9S3hM3kHFqOL
f8Ua/ygYnWgAe7XeR7pxC9N1wRZHUbBXEc+I8hQa0i3a0vM0j62c2xQZ/tF7/wwy
1ie/7ogU2+4CCAqXUU783I9HtZC+kGeNGPtuBMgQUlwJ96NavK7fxCvLRRejs+Pc
9AhPYSQcGF/abeqVxSib2QBnXUumWXWKKPNSqpVvKWgTjGhtE0HNjHHq+y5tv3pi
l7IlyK3eR4jGbDxxswUkFo0be1OU/LKP9jKM0nNB+GT3OT5Xu6qV2lDQIpAe3r/i
E1yGZXTe+WlfhVbtaz6KQKqa4wf9nF85JMu3lfwigAucxIbfrcMkXKEnrROq9qpw
5ouNyUTrbPgnap5v8JUMNmKp2PgR87v9ZUwtwum2w7FH5+qzGGGC+5dGnwC9JiUj
9G0ETBaUnMkqcTRAUyz9q+BHdgD9+ZWIfw3U4Db23YtDEtwwHcZgZDg2TA7Ch6jm
EY+h/UWs3jYNjT4ZTulx
=V736
-END PGP SIGNATURE-

[gentoo-dev] [PATCH v3 19/21] general-concepts/tree: remove the reference to the ChangeLog #485314

[gokturk]

From: Gokturk Yuksek 

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=485314
Signed-off-by: Gokturk Yuksek 
---
 general-concepts/tree/text.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/general-concepts/tree/text.xml b/general-concepts/tree/text.xml
index 6f59f09..877b8f4 100644
--- a/general-concepts/tree/text.xml
+++ b/general-concepts/tree/text.xml
@@ -17,7 +17,6 @@ The basic layout of the portage tree is as follows:
 Package directories for example app-editors/vim
 
   Package metadata, for example 
app-editors/vim/metadata.xml
-  Package changelog, for example app-editors/vim/ChangeLog
   Package Manifest, for example app-editors/vim/Manifest
   
   Ebuilds, for example app-editors/vim/vim-6.3.068.ebuild,
-- 
2.4.10

[gentoo-dev] [PATCH v3 21/21] ebuild-writing/user-submitted: mention git style tags in commit messages #558642

[gokturk]

From: Gokturk Yuksek 

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-writing/user-submitted/text.xml | 4 
 1 file changed, 4 insertions(+)

diff --git a/ebuild-writing/user-submitted/text.xml 
b/ebuild-writing/user-submitted/text.xml
index a148042..68c88f0 100644
--- a/ebuild-writing/user-submitted/text.xml
+++ b/ebuild-writing/user-submitted/text.xml
@@ -22,6 +22,10 @@ The user-submitted ebuild must not contain custom headers 
like this:
 
 
 Such information should be included in the git commit message instead.
+The use of tags such as Suggested-By: or Reported-By:in
+the commit message, as explained in the
+commit
+message format section, is highly encouraged.
 Note that ebuilds received in the form of git patches or pull requests
 will have the user as the commit author by default, in which case
 including the user information in the commit message explicitly
-- 
2.4.10

[gentoo-dev] [PATCH v3 15/21] general-concepts/git-to-rsync/diagram: update the description for git #558642

[gokturk]

From: Gokturk Yuksek 

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 general-concepts/git-to-rsync/diagram.svg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/general-concepts/git-to-rsync/diagram.svg 
b/general-concepts/git-to-rsync/diagram.svg
index 8cf7414..2ee9608 100644
--- a/general-concepts/git-to-rsync/diagram.svg
+++ b/general-concepts/git-to-rsync/diagram.svg
@@ -2,7 +2,7 @@
 http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
 http://www.w3.org/2000/svg"; version="1.1">
-CVS to RSYNC Propagation
+Git to RSYNC Propagation
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 16/21] general-concepts/git-to-rsync/diagram: update the description for git #558642

[gokturk]

From: Gokturk Yuksek 

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 general-concepts/mirrors/diagram.svg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/general-concepts/mirrors/diagram.svg 
b/general-concepts/mirrors/diagram.svg
index 0af1f1c..b807e5a 100644
--- a/general-concepts/mirrors/diagram.svg
+++ b/general-concepts/mirrors/diagram.svg
@@ -52,7 +52,7 @@
   
   CVS to RSYNC Propagation
+ id="desc1548">Git to RSYNC Propagation
   

[gentoo-dev] [PATCH v3 17/21] ebuild-writing/misc-files: remove ChangeLog section #485314

[gokturk]

From: Michael Orlitzky 

The ChangeLog section under misc-files is misleading now that our main
repository has been switched to git (and we no longer have
ChangeLogs). Remove the ebuild-writing/misc-files/changelog page.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=485314
---
 ebuild-writing/misc-files/changelog/text.xml | 111 ---
 ebuild-writing/misc-files/text.xml   |   1 -
 2 files changed, 112 deletions(-)
 delete mode 100644 ebuild-writing/misc-files/changelog/text.xml

diff --git a/ebuild-writing/misc-files/changelog/text.xml 
b/ebuild-writing/misc-files/changelog/text.xml
deleted file mode 100644
index ff68e11..000
--- a/ebuild-writing/misc-files/changelog/text.xml
+++ /dev/null
@@ -1,111 +0,0 @@
-
-
-
-ChangeLog
-
-
-
-The ChangeLog must be updated with each commit. The
-echangelog tool should be used 
to create ChangeLog entries;
-the format of a ChangeLog is now defined as "whatever
-echangelog creates".
-
-
-
-You should include references to any relevant bugs. The standard
-format for doing this is via the phrase bug #20600 — this
-format (with the hash sign included) is recognised via
-https://packages.gentoo.org";>packages.gentoo.org and
-similar tools. When including user-submitted ebuilds or patches, you
-should credit the user with their full name and email address (or
-whatever they use to identify themselves on bugzilla  some users
-prefer to be known only by a nickname).
-
-
-
-If you are changing keywords, make sure you clearly state what
-keywords you add or remove. "Marked stable" is a nuisance for
-architecture teams, even if there was only one keyword in the ebuild
-at the time. "Stable on all archs" isn't generally any better (and
-should you really be stabling on all archs?) — do you mean "all", or
-"all the ones that are currently keyworded"? A list like "x86 sparc
-mips" is much more useful.
-
-
-
-A typical ChangeLog snippet might look like the following:
-
-
-
-*vim-6.3.068 (25 Mar 2005)
-
-  25 Mar 2005; Ciaran McCreesh  
+vim-6.3.068.ebuild:
-  New release. Fixes bug #79981, bug #81289, bug #83383, bug #83416, bug
-  #83565, bug #85758, upstream patches up to 6.3.068.
-
-  22 Mar 2005; Aron Griffis  vim-6.3-r4.ebuild:
-  Stable on alpha
-
-
-
-If a ChangeLog file is not present in your current working directory,
-then you should write a ChangeLog entry in the parent's directory
-ChangeLog file.
-
-
-
-Writing correct ChangeLog messages
-
-
-It is very important that your cvs commit messages are
-also informative to aid the QA team or architecture teams as well as
-other developers if they are trying to troubleshoot issues which are
-known to not have occured in previous versions of ebuilds, for
-example. If your ChangeLog message is concise there is usually nothing
-wrong with using it as the cvs commit message.
-
-
-
-Your message should explain what specifically you changed and, if
-relevant, why. You don't need to write an essay or even a complete
-sentence (ChangeLog messages, however, are required to be in
-'proper' English so no fixed that bug kthx Bob messages —
-please do use punctuation), so long as it is easily understandable and
-(preferably) greppable. Bad and good examples, all of which are based
-upon real messages:
-
-
-
-  BAD: Changed keywords
-  GOOD: Added ~x86 keyword
-
-
-
-  BAD: Stable
-  GOOD: Stable on x86, sparc, mips
-
-
-
-  BAD: Fix stuff
-  GOOD: Fix USE=foo logic error
-
-
-
-  BAD: .
-  GOOD: Purge old ebuilds
-
-
-
-  
-BAD: Who the fuck reads this anyway? (Editor's note:
-No, seriously, this is a genuine example. Do not do
-this...)
-  
-  GOOD: Version bump to 0.5.1.
-
-
-
-
-
-
-
diff --git a/ebuild-writing/misc-files/text.xml 
b/ebuild-writing/misc-files/text.xml
index 31f1421..416070b 100644
--- a/ebuild-writing/misc-files/text.xml
+++ b/ebuild-writing/misc-files/text.xml
@@ -18,6 +18,5 @@ This section contains some notes on various miscellaneous 
files.
 
 
 
-
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 20/21] ebuid-maintenance: add a new section called "Git Commit Message Format" #558642

[gokturk]

From: Gokturk Yuksek 

This section includes the content from the "Commit message format"
subsection on Gentoo git workflow wiki page, combines it with some of
the information that was part of the old ChangeLog section in
devmanual and expands on those based on the feedback from the developers
on the gentoo-dev@g.o mailing list.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Reviewed-by: NP-Hardass 
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 113 
 1 file changed, 113 insertions(+)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 26cca2f..5b2abee 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -96,6 +96,119 @@ work on those architectures.
 
 
 
+Git Commit Message Format
+
+
+
+It is important to format the commit messages properly so that they
+communicate the changes to the reader in a clear and concise
+way. Additionally, consistency in message format allows for easier
+parsing by external tools. The first line of the commit message should
+contain a brief summary of the changes, followed by an empty new
+line. From the third line onward should be a detailed, multiline
+explanation of the changes introduced by the commit. At the very end,
+auxiliary information such as the bugs related to the commit,
+contributors, and reviewers should be listed using RFC822/git style
+tags. The length of the lines in the message should be 70-75
+characters at maximum.
+
+
+
+The summary line should start with referencing what is affected by the
+change followed by a colon ':' character. Use the rules in the
+following list to determine the proper format based on what has
+changed, substituting the package, category and eclass names
+appropriately:
+
+
+${CATEGORY}/${PN}:Single Package (Note that repoman commit
+automatically inserts this for you)
+${CATEGORY}: Package Category
+profiles: Profile Directory
+${ECLASS}.eclass: Eclass Directotry
+licenses: Licenses Directory
+metadata: Metadata Directory
+
+
+For packages where ${CATEGORY}/${PN}: is long, the line length
+limit can be exceeded, if absolutely necessary, to ensure a more
+useful summary line. If a commit affects multiple directories, prepend
+the message with which reflects the intention of the change best. If
+there are any bugs on Gentoo Bugzilla associated with the commit, id
+of the bug can be appended to the summary line using the format
+#BUG-ID. If you are modifying keywords, clearly state what
+keywords are added/removed.
+
+
+By default, lines starting with # are considered to be comments
+by git and not included in the commit message. Make sure that a new
+line does not start with #BUG-ID. Optionally, git can be
+configured to use a different character for comments by changing the
+commentchar option.
+
+
+
+
+For non-trivial commits, the message should contain a detailed
+explanation of what the commit intends to change, why it is required,
+and how it is accomplished, along with any other supplementary
+information.
+
+
+
+Finally the commit message should list auxiliary information such as
+people who are involved in authoring, suggesting, reviewing and
+testing the changes, and revelant bugs. Use RFC822/git style tags as
+explained in the
+https://www.kernel.org/doc/Documentation/SubmittingPatches";>
+Linux Kernel patch guideline. Additionally, the following tags
+are used in Gentoo:
+
+
+Gentoo-Bug: Use this to reference bugs in Gentoo Bugzilla
+by either the bug ID or the bugzilla URI. Multiple bugs can be
+referenced by inserting more tags of this type or separating bug IDs
+with a comma in the same tag. The bug IDs may include an optional '#'
+prefix. There is no consensus on referencing bugs in the summary line
+versus referencing with a tag in the message body. The developer has
+the option to choose either.
+
+Package-Manager: This is automatically inserted by
+repoman commit and it specifies the version of
+sys-apps/portage on the system.
+RepoMan-Options: This is automatically inserted by
+repoman commit and records the options passed to repoman (such
+as --force) for the commit.
+
+
+
+
+When committing user
+contributions, make sure to credit them in your commit message
+with the user's full name and email address. Be aware and respectful
+of their privacy: some users prefer to be only known by a
+nickname. Take advantage of the tags such as Suggested-By or
+Reported-By:when entering such information to the commit
+message.
+
+
+
+An example commit message is shown below:
+
+
+
+app-misc/foo: version bump to 0.5
+
+This also adds a new USE flag 'bar' which controls the
+new bar functionality introduced with this version.
+
+Gentoo-Bug: 01234
+
+
+
+
+
+
 Git Commit Policy
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 14/21] ebuild-maintenance: replace "cvs commit" with "git commit" #558642

[gokturk]

From: Gokturk Yuksek 

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index b9c6327..26cca2f 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -62,8 +62,8 @@ examples.
 
 
 
-When committing to CVS, all developers should use repoman commit 
-instead of cvs commit to submit their ebuilds.  Before committing, 
+When committing to git, all developers should use repoman commit
+instead of git commit to submit their ebuilds.  Before committing,
 please run repoman full to make sure you didn't forget something.
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 18/21] tools-reference: remove the echangelog page #485314

[gokturk]

From: Michael Orlitzky 

Since the switch to git, developers should never need to use
echangelog. Remove its page from the tools-reference section.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=485314
---
 tools-reference/echangelog/text.xml | 32 
 tools-reference/text.xml|  1 -
 2 files changed, 33 deletions(-)
 delete mode 100644 tools-reference/echangelog/text.xml

diff --git a/tools-reference/echangelog/text.xml 
b/tools-reference/echangelog/text.xml
deleted file mode 100644
index 567dad9..000
--- a/tools-reference/echangelog/text.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
-echangelog -- ChangeLog Generation
-
-
-
-The echangelog tool should be used to generate ChangeLog
-entries. This tool uses the ECHANGELOG_USER environment
-variable, which should be set in the format "Your Name
-". The changelog message should be passed to
-echangelog on the commandline, or otherwise echangelog
-will open an editor for you to type your message.
-
-
-
-echangelog should be called after any adds, removes or
-updates have been made.
-
-
-
-See echangelog-1 for details.
-
-
-
-The echangelog tool is considered deprecated as repoman commit -m 
"[your message here]"
- will create a ChangeLog entry automatically when used for commits in the 
portage tree.
-
-
-
-
-
diff --git a/tools-reference/text.xml b/tools-reference/text.xml
index a4cadf8..9e0f6bc 100644
--- a/tools-reference/text.xml
+++ b/tools-reference/text.xml
@@ -23,7 +23,6 @@ ebuilds.
 
 
 
-
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 13/21] ebuild-maintenance: rewrite the subsection on removing packages for git #558642

[gokturk]

From: Gokturk Yuksek 

Substitute the mentions of CVS with git.
Rewrite CVS commands with their git equivalents.
Remove the paragraph about deleting directories in CVS.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 28 +---
 1 file changed, 21 insertions(+), 7 deletions(-)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index d388d6d..b9c6327 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -428,20 +428,34 @@ When removing packages follow these steps:
   Send last rites to gentoo-dev-announce and gentoo-dev
   Mask the package
   Wait 30 days (or more)
-  Remove from CVS unless the reason for removal has been fixed
+  Remove from the git tree unless the reason for removal has been 
fixed
   Remove package.mask entry
   Close open bugs as WONTFIX
  
 
 
-In order to remove a package completely from CVS, delete any files from the
-directory and commit this, CVS will take care of removing empty directories
-itself.
+Here is a list of commands that will delete dev-util/pmk
+from the tree:
 
 
-# 
cd app-admin
-# cvs rm -Rf scotty
-# cvs ci -m "app-admin/scotty removal 
(pending 21st July 2006), see #77501 for reference." scotty
+
+# cd dev-util
+# git rm -rf pmk
+# git commit --gpg-sign
+
+
+An example commit message is shown below:
+
+
+
+commit e0bbcf8291501dc7de6b4b120d4372061367dd7a
+Author: Michael Palimaka 
+Date:   Fri Jan 29 07:11:01 2016 +1100
+
+  dev-util/pmk: remove last-rited package
+
+  Gentoo-bug: 541522
+
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 12/21] ebuild-maintenance: rewrite the subsection on removing ebuilds for git #558642

[gokturk]

From: Gokturk Yuksek 

Substitute the mentions of CVS with git.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 74ef88b..d388d6d 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -396,8 +396,8 @@ entry which may be affected by your change.
 
 
 When removing an ebuild make sure that no dependencies in Portage are broken
-due to the removal - additionally, your CVS commit message should explain
-clearly why the ebuild is being removed from CVS.
+due to the removal - additionally, your git commit message should explain
+clearly why the ebuild is being removed from the git repository.
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 11/21] ebuild-maintenance: rewrite the subsection on moving ebuilds for git #558642

[gokturk]

From: Gokturk Yuksek 

Rename the subsection to "moving a package" and rewrite it from scratch.
The previous workflow suggested a 2 step process whereas the new one
suggests a single git commit to contain all the changes.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 92 +
 1 file changed, 59 insertions(+), 33 deletions(-)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 28442a3..74ef88b 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -290,56 +290,82 @@ to be in very poor taste and may result in disciplinary 
action.
 
 
 
-Moving ebuilds
+Moving a package
 
 
 
-Moving ebuilds is a two-step process:
+Moving a package in the tree requires several operations. Firstly,
+the package directory needs to be moved to the correct category
+using git mv. After this, a new entry needs to be added to
+the latest file in profiles/updates/ in the
+following format:
 
 
-
-Firstly, you need to move the ebuild in CVS. To do this, you should
-copy the ebuild to its new location and commit that as you would with
-a new ebuild.
-
+
+move old-category/package-name new-category/package-name
+
 
 
-After this, you should change any ebuilds which DEPEND on the
-old ebuild to depend on the new one. After this, should add an entry to the
-latest file in profiles/updates/ in the Portage tree in the in
-the following format:
+Following the update entry, ebuilds that have a
+dependency
+to this package (in other words, the reverse dependencies of
+the package to be moved) need to be updated properly.
 
 
-
-move net-misc/fwbuilder net-firewall/fwbuilder
-
-
 
-This example would transparently move net-misc/fwbuilder to
-net-firewall/fwbuilder if users have it installed. This
-way, users would now automatically receive updates
-for net-firewall/fwbuilder when they are available.
+Next is checking the files under profiles/ such as
+profiles/package.mask and update them to reflect the ebuild
+move. Various eclasses automatically provide some of the dependencies upon
+inherit, so the files under eclass/ should be checked and updated
+properly as well. Lastly, the titles of the open bugs related to the package
+should be updated.
 
 
 
-Once this step is concluded, you are allowed to remove the old package.
-Simply issue a cvs remove -Rf $PN in the package category and commit
-the changes afterwards with a meaningful commit message. Don't forget to update
-entries in files such as profiles/package.mask to reflect the new category. 
Finally
-remember to change the title to open bugs related to this package if needed.
+Here is an example where the package
+net-misc/fwbuilder is transparently moved to
+net-firewall/fwbuilder:
 
 
-
-net-misc # cvs rm -Rf fwbuilder
-cvs remove: use `cvs commit' to remove these files permanently
-net-misc # cvs ci -m "Moving net-misc/fwbuilder to net-firewall/fwbuilder."
+
+  Issue git mv net-misc/fwbuilder net-firewall/fwbuilder
+  
+
+  Add the following entry to the latest file in
+  profile/updates/:
+
+move net-misc/fwbuilder net-firewall/fwbuilder
+  
+  Update the reverse dependencies of the package
+  
+Update profiles/package.mask and other related files under
+profiles/
+  
+  Check the eclasses that may be referencing the package
+  
+Stage all the changed files using git add. For example: git add
+profiles/package.mask
+  
+  
+Commit all the changes in one commit using: git commit --gpg-sign
+  
+  Update any open bugs related to the package
+
+
+
+It is very important to commit all the changes in a single commit to ensure
+that no breakage occurs. The commit message should follow a format similar
+to the following:
+
+
+
+commit d391643289097344a0b18ab2665bb26198a0e3a1
+Author: Guilherme Amadio 
+Date:   Tue Nov 3 20:26:52 2015 +0100
+
+  media-fonts/nanumfont: renamed to media-fonts/nanum
 
 
-
-CVS cannot destroy directories: it will simply not re-create them if
-they are blank, providing you use CVS with the -P flag.
-
-
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 10/21] ebuild-maintenance: rewrite the subsection on upgrading ebuilds for git #558642

[gokturk]

From: Gokturk Yuksek 

Substitute the mentions of CVS with git.
Rewrite CVS commands with their git equivalents.
Delete the reference to editing ChangeLog.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 9372895..28442a3 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -275,14 +275,14 @@ available.
 
 
 If there are no new dependencies, do not remove keywords if your
-commit fails with repoman - please try a full cvs update and if
+commit fails with repoman - please try a full git pull and if
 you still have problems, then commit with repoman -I and file a
-bug to the broken architecture, noting it in your CVS commit message.
+bug to the broken architecture, noting it in your git commit message.
 
 
 
 When committing, make sure that you reference any bugs in the
-ChangeLog as well as the CVS message. Failing to do so is considered
+commit message. Failing to do so is considered
 to be in very poor taste and may result in disciplinary action.
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 09/21] ebuild-maintenance: rewrite the subsection on commit policy for git #558642

[gokturk]

From: Gokturk Yuksek 

Remove the mention of updating the ChangeLog.
Remove the mention of file conflicts during commit as CVS keeps track of
files whereas git keeps track of changesets.

Add a note regarding commit atomicity: Git commits are always atomic, so
combining package.mask/license changes with ebuild changes in the same
commit does not violate atomicity. However, there is no way to accomplish
this using repoman commit.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 15 +--
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 3cefdc2..9372895 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -96,7 +96,7 @@ work on those architectures.
 
 
 
-CVS Commit Policy
+Git Commit Policy
 
 
 
@@ -105,15 +105,18 @@ work on those architectures.
 Always test that package.mask is okay by doing 
 emerge --pretend mypkg before you commit and check 
 that it doesn't contain any conflicts.
-Always update the ChangeLog before you commit.
-Always commit the updated package.mask before 
-the updated package, in case conflicts occur while you commit 
-package.mask.
+Always commit the updated package.mask before
+the updated package.
 Always do atomic commits; if you commit a package with a new license, 
 or that is masked, then first commit the revised package.mask 
and/or license, 
 then commit the ebuild, ChangeLog, patches
 and metadata.xml all in 
one go
-to avoid breaking users' installations.
+.
+ Although the set of changes in a single git commit is atomic, and
+combining package.mask/license changes with ebuild changes in a
+single commit wouldn't break atomicity, it is not currently possible to do so
+using repoman commit.
+
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 07/21] appendices/editor-configuration/emacs: remove the CVS related setting #558642

[gokturk]

From: Gokturk Yuksek 

Setting vc-cvs-stay-local to nil causes VC to query the remote repository.
Git is a distributed VCS. As such no equivalent command exists for git.
Remove the CVS related setting.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 appendices/editor-configuration/emacs/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/appendices/editor-configuration/emacs/text.xml 
b/appendices/editor-configuration/emacs/text.xml
index 55fade0..0a5e38d 100644
--- a/appendices/editor-configuration/emacs/text.xml
+++ b/appendices/editor-configuration/emacs/text.xml
@@ -47,8 +47,8 @@ automatically check for the existence of it and ask you to 
add one.
 
 
 Other useful settings can be disabled backup files
-(by (setq make-backup-files nil) and
-(setq vc-cvs-stay-local nil)), so you don't clutter CVS
+(by (setq make-backup-files nil), so you don't clutter the git
+repository
 directories and confuse repoman with it (by adding unnecessary entries
 into a Manifest file e.g.). Emacs can even contact the outside world
 by using the X servers clipboard abilities when yanking, which is
-- 
2.4.10

[gentoo-dev] [PATCH v3 08/21] ebuild-maintenance: rewrite the text on adding binary files to the tree #558642

[gokturk]

From: Gokturk Yuksek 

Remove the paragraph about adding binary files to CVS.
Replace the instances of CVS with git.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-maintenance/text.xml | 19 +++
 1 file changed, 3 insertions(+), 16 deletions(-)

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index ac68dcd..3cefdc2 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -42,22 +42,9 @@ above 20KB) which should be distributed as tarballs via the
 Gentoo mirror 
system
 so that people do not waste excessive amounts of bandwidth and hard drive
 space. Also, you should not add binary (non-ASCII) files to the
-Portage CVS tree. If you need to do this in another CVS tree, for
-example, if you need to add a small PNG graphic for whatever reason,
-be sure to add it to CVS by using the -kb option, like so:
-
-
-
-# cvs add -kb myphoto.png
-
-
-
-The -kb option tells CVS that myphoto.png is a binary
-file and should be treated specially.  For example, merging the 
-differences between two different versions of this file should not be 
-allowed to happen, for obvious reasons.  Also, speaking of merging 
+git tree. Also, speaking of merging
 changes, any patches you add to Portage should generally not be 
-compressed.  This will allow CVS to merge changes and correctly inform 
+compressed.  This will allow git to merge changes and correctly inform
 developers of conflicts.
 
 
@@ -149,7 +136,7 @@ simply, 1.0-gentoo.diff.  Also note that the
 gentoo extension informs people that this patch was created 
 by us, the Gentoo Linux developers, rather than having been grabbed from a 
 mailing list or somewhere else. Again, you should not compress these 
-patches because CVS does not play well with binary files.
+patches.
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 04/21] general-concepts/tree: replace the mention of ChangeLog #558642

[gokturk]

From: Gokturk Yuksek 

Package updates do not require changing of the ChangeLog file. Package
updates by users that do not mention what has changed is still
considered a common mistake however.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-writing/common-mistakes/text.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ebuild-writing/common-mistakes/text.xml 
b/ebuild-writing/common-mistakes/text.xml
index 1718d55..1716e5d 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -468,7 +468,7 @@ of the application, if any exists.
 
 
 
-Package updates without changing the ChangeLog
+Package updates without explaining what has changed
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 03/21] general-concepts/tree: substitute "CVS" with "git" #558642

[gokturk]

From: Gokturk Yuksek 

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 general-concepts/tree/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/general-concepts/tree/text.xml b/general-concepts/tree/text.xml
index 022a1ea..6f59f09 100644
--- a/general-concepts/tree/text.xml
+++ b/general-concepts/tree/text.xml
@@ -59,11 +59,11 @@ The basic layout of the portage tree is as follows:
   Scripts directory, scripts/
   
   Distfiles directory, distfiles/. This is not included in the main
-  CVS tree, but it will be found on most user systems.
+  git tree, but it will be found on most user systems.
   
   
   Packages directory, packages. Again, this is found on user systems 
but not
-  in the main CVS tree.
+  in the main git tree.
   
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 06/21] ebuild-writing/user-submitted: do not put user information in ChangeLog #558642

[gokturk]

From: Gokturk Yuksek 

ChangeLog files are auto-generated by infra post git-migration.
For user-submitted ebuilds, include the user information in the commit
message instead. Mention that user submitted git patches and pull
requests preserve the authorship information by default.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-writing/user-submitted/text.xml | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/ebuild-writing/user-submitted/text.xml 
b/ebuild-writing/user-submitted/text.xml
index ef80c0d..a148042 100644
--- a/ebuild-writing/user-submitted/text.xml
+++ b/ebuild-writing/user-submitted/text.xml
@@ -16,14 +16,16 @@ the ebuild meets all Gentoo Linux development standards.
 The user-submitted ebuild must not contain custom headers like this:
 
 
-
+
 # Ebuild updated by: me 
 
 
 
-Such information should be added to the ChangeLog instead.
-The first ChangeLog entry should always credit the user who
-submitted the ebuild, with their full name and e-mail address.
+Such information should be included in the git commit message instead.
+Note that ebuilds received in the form of git patches or pull requests
+will have the user as the commit author by default, in which case
+including the user information in the commit message explicitly
+may not be necessary.
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 05/21] ebuild-writing/misc-files: replace the code for cvs commit with git #558642

[gokturk]

From: Gokturk Yuksek 

Replace "cvs commit" with the equivalent "git add && git commit" version.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 ebuild-writing/misc-files/metadata/text.xml | 16 +++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/ebuild-writing/misc-files/metadata/text.xml 
b/ebuild-writing/misc-files/metadata/text.xml
index e506b1c..2de3cf5 100644
--- a/ebuild-writing/misc-files/metadata/text.xml
+++ b/ebuild-writing/misc-files/metadata/text.xml
@@ -532,7 +532,21 @@ is currently:
 
 xmllint --noout --valid metadata.xml
 glep31check metadata.xml
-cvs commit -m "Adding category metadata.xml for my-category" metadata.xml
+git add metadata.xml
+git commit --gpg-sign
+
+
+
+The commit message should be formatted properly.
+A sample commit is shown below:
+
+
+
+commit db359439bcd52f5a7f20d2332ab62feb16657504
+Author: Alexis Ballier 
+Date:   Tue Sep 22 10:47:49 2015 +0200
+
+  dev-ros: Add metadata.xml for the category.
 
 
 
-- 
2.4.10

[gentoo-dev] [PATCH v3 02/21] general-concepts/mirrors: substitute "CVS" with "the git tree" #558642

[gokturk]

From: Gokturk Yuksek 

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 general-concepts/mirrors/text.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/general-concepts/mirrors/text.xml 
b/general-concepts/mirrors/text.xml
index e860988..6e3386a 100644
--- a/general-concepts/mirrors/text.xml
+++ b/general-concepts/mirrors/text.xml
@@ -55,7 +55,7 @@ On rare occasions you may need to replace a file that is 
already mirrored.  In t
 follows:
 
   Put a copy of the new distfile on dev.gentoo.org into 
/space/distfiles-local
-  commit the new manifest to CVS
+  commit the new manifest to the git tree
   wait
 
 After a few hours a cron job on dev.gentoo.org will fetch the file and replace 
the version on the
-- 
2.4.10

[gentoo-dev] [PATCH v3 00/21] devmanual: update the docs for post git-migration

[gokturk]

From: Gokturk Yuksek 

Hi,

This is the third iteration of the patch series that attempts to
update the devmanual for the git migration.

The updates included in the third revision are:
- Added a new subsection called "Git Commit Message Format" based on
  the commit message format included in the Gentoo Git Workflow wiki
  and the feedback provided on this mailing list.
- Based on the discussion wrt how well git deals with compressed
  patches, I've decided to remove "because git does not play well with
  binary files".  It's a policy we have been following for years
  irrespective of how git deals with them.
- Rewrote the subsection on "Removing a package" so it does not use
  'git commit -m'. Rewrote the example and added the corresponding
  commit message as an example.
- The subsection "User-submitted Ebuilds" is modified to mention the
  use of git style tags in commit messages and a reference to the
  commit message format policy section has been added.

You can review the changes on Github for your own convenience:
https://github.com/gktrk/devmanual.gentoo.org/compare/master...gktrk:devmanual-git-migration-v3

If you want to see the diff between v2 and v3, you can clone the
Github repo and check the diff between the branches
"devmanual-git-migration-v2" and "devmanual-git-migration-v3".

The HTML version of the devmanual with the proposed changes can be found at:
http://devmanual.qui-gon.org/

Gokturk Yuksek (19):
  general-concepts/manifest: drop the use of "CVS keyword expansion"
#558642
  general-concepts/mirrors: substitute "CVS" with "the git tree" #558642
  general-concepts/tree: substitute "CVS" with "git" #558642
  general-concepts/tree: replace the mention of ChangeLog #558642
  ebuild-writing/misc-files: replace the code for cvs commit with git
#558642
  ebuild-writing/user-submitted: do not put user information in
ChangeLog #558642
  appendices/editor-configuration/emacs: remove the CVS related setting
#558642
  ebuild-maintenance: rewrite the text on adding binary files to the
tree #558642
  ebuild-maintenance: rewrite the subsection on commit policy for git
#558642
  ebuild-maintenance: rewrite the subsection on upgrading ebuilds for
git #558642
  ebuild-maintenance: rewrite the subsection on moving ebuilds for git
#558642
  ebuild-maintenance: rewrite the subsection on removing ebuilds for git
#558642
  ebuild-maintenance: rewrite the subsection on removing packages for
git #558642
  ebuild-maintenance: replace "cvs commit" with "git commit" #558642
  general-concepts/git-to-rsync/diagram: update the description for git
#558642
  general-concepts/git-to-rsync/diagram: update the description for git
#558642
  general-concepts/tree: remove the reference to the ChangeLog #485314
  ebuid-maintenance: add a new section called "Git Commit Message
Format" #558642
  ebuild-writing/user-submitted: mention git style tags in commit
messages #558642

Michael Orlitzky (2):
  ebuild-writing/misc-files: remove ChangeLog section #485314
  tools-reference: remove the echangelog page #485314

 appendices/editor-configuration/emacs/text.xml |   4 +-
 ebuild-maintenance/text.xml| 281 +++--
 ebuild-writing/common-mistakes/text.xml|   2 +-
 ebuild-writing/misc-files/changelog/text.xml   | 111 --
 ebuild-writing/misc-files/metadata/text.xml|  16 +-
 ebuild-writing/misc-files/text.xml |   1 -
 ebuild-writing/user-submitted/text.xml |  14 +-
 general-concepts/git-to-rsync/diagram.svg  |   2 +-
 general-concepts/manifest/text.xml |   4 +-
 general-concepts/mirrors/diagram.svg   |   2 +-
 general-concepts/mirrors/text.xml  |   2 +-
 general-concepts/tree/text.xml |   5 +-
 tools-reference/echangelog/text.xml|  32 ---
 tools-reference/text.xml   |   1 -
 14 files changed, 247 insertions(+), 230 deletions(-)
 delete mode 100644 ebuild-writing/misc-files/changelog/text.xml
 delete mode 100644 tools-reference/echangelog/text.xml

-- 
2.4.10

[gentoo-dev] [PATCH v3 01/21] general-concepts/manifest: drop the use of "CVS keyword expansion" #558642

[gokturk]

From: Gokturk Yuksek 

With the git migration no CVS keyword expansions are happening. However,
Manifest file may still need to be regenerated.

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642
Signed-off-by: Gokturk Yuksek 
---
 general-concepts/manifest/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/general-concepts/manifest/text.xml 
b/general-concepts/manifest/text.xml
index 27ebdef..12961da 100644
--- a/general-concepts/manifest/text.xml
+++ b/general-concepts/manifest/text.xml
@@ -18,8 +18,8 @@ The Manifest may also be digitally signed.
 
 
 To generate the Manifest, use ebuild foo.ebuild manifest. When
-committing, the Manifest file must be regenerated to handle any CVS 
keyword
-expansion changes  repoman will do this automatically.
+committing, the Manifest file must be regenerated to handle any
+changes  repoman will do this automatically.
 
 
 
-- 
2.4.10

[gentoo-dev] Last rites: dev-java/{concurrent-util,dsiutils,sux4j}

[James Le Cuirot]

# James Le Cuirot  (03 Feb 2016)
# Built into Java since 1.5. Ancient and doesn't build with
# Java 8. Removal in 30 days. See bug #544038.
dev-java/concurrent-util

# James Le Cuirot  (03 Feb 2016)
# Old, unused, broken on Java 7 and up. These are still alive upstream
# but bumping is likely non-trivial. Removal in 30 days.
dev-java/dsiutils
dev-java/sux4j

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer


pgpTbZTZeXomT.pgp
Description: OpenPGP digital signature

[gentoo-dev] Re: [PATCH 0/5] RFC: Patches for wxwidgets.eclass

[Ryan Hill]

On Wed, 3 Feb 2016 10:21:40 +0100
"Justin Lecher (jlec)"  wrote:

> On 02/02/16 23:36, Ryan Hill wrote:
> > On Mon,  1 Feb 2016 12:08:28 +0100
> > Justin Lecher  wrote:
> >   
> >> while tracking down the following error when running "egencache"
> >>
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
> >>
> >> I found that the global scope get_libdir() usage of the wxwidgets.eclass
> >> doens't work on EAPI=6. The following patches correct some minor things
> >> and block EAPI=6 for now until the eclass is ready.
> >>
> >> Justin Lecher (5):
> >>   wxwidgets.eclass: Update Copyright year
> >>   wxwidgets.eclass: Fix whitespaces
> >>   wxwidgets.eclass: unset unneeded variables in global scope after usage
> >>   wxwidgets.eclass: Only inherit eclass ones
> >>   wxwidgets.eclass: Add EAPI support
> >>
> >>  eclass/wxwidgets.eclass | 33 -
> >>  1 file changed, 24 insertions(+), 9 deletions(-)
> >>  
> > 
> > 1. I don't think most of this is necessary but go ahead I guess.  
> 
> Most of them are trivial, but excluding EAPI=6 from supported EAPIs is
> essential. The usage of get_libdir needs to be moved to a phase
> function. Which should perhaps be coupled with an env variable which is
> checked in the later function to ensure the phase function has been run.

Yeah, it just kind of screws us from getting sane defaults just by inheriting
the eclass.  I guess we'll have to find another way.

> > 2. When did we start posting every @&#$! eclass change to g-dev?  File a bug
> > like a normal person.  (There's already one open you could have used)  
> 
> I feel pretty "normal" when sending eclass changes to g-dev. Having code
> reviewed which influences a larger number of packages at once in the
> most public and open way is something we should strive for, isn't it?

Yes, thanks and sorry for being crabby.

-- 


pgpHWgHsFmvfM.pgp
Description: OpenPGP digital signature

Re: [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM

[Michał Górny]

On Wed, 3 Feb 2016 23:29:49 +0100
Manuel Rüger  wrote:

> Hello gentoo-dev,
> 
> I'd like to announce the NGINX_MODULES_STREAM use expand.
> 
> It will include nginx modules used for stream support.
> Initially, there will be the following descriptions included:
> 
> 
> access - This module allows limiting access to certain client addresses.
> limit_conn - This module is used to limit the number of connections per
> the defined key.
> upstream - This module is used to define groups of servers that can be
> referenced by the proxy_pass directive.

Could we please finally stop introducing global USE flags that are
going to only be used by a single package? make.conf already looks like
random mix of randoms these days, with some extra random cruft being
added every second Tuesday.

-- 
Best regards,
Michał Górny



pgpvd7mb7DhYU.pgp
Description: OpenPGP digital signature

[gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM

[Manuel Rüger]

Hello gentoo-dev,

I'd like to announce the NGINX_MODULES_STREAM use expand.

It will include nginx modules used for stream support.
Initially, there will be the following descriptions included:


access - This module allows limiting access to certain client addresses.
limit_conn - This module is used to limit the number of connections per
the defined key.
upstream - This module is used to define groups of servers that can be
referenced by the proxy_pass directive.


Cheers,

Manuel



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-dev] [Fwd: [gentoo-automated-testing] BROKEN: repository became broken!]

[Andreas K. Huettel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Dienstag, 2. Februar 2016, 02:33:30 schrieb Mike Frysinger:
>
> > I took the liberty of doing (2) and reverted the commit. Not sure why
> > this needs so much discussion; after all a broken tree is always
> > suboptimal.
> 
> unless things are on fire (which i don't think this was), i don't
> generally clamor for 0-day fixes.  if we can find a better fix in
> a day or so, then i'm happy for that.  i dislike repos with history
> that is just a constant stream of land, revert, land, revert, land.
> 
> not that i'm saying your revert was wrong ... just airing my
> general personal preferences.

You're right of course... but there's one thing we have to keep in mind.

We're not running a project were releases are made from the vcs. The vcs *is* 
the release... and whatever is out there gets pushed to users.

This is why my personal preference is more to revert if I'm not sure that the 
fix will happen soon.

- -- 

Andreas K. Huettel
Gentoo Linux developer 
dilfri...@gentoo.org
http://www.akhuettel.de/

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1

iQJ8BAEBCgBmBQJWsnK8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDMjhGQ0IwRjdCRUQxMzdBQUNCMDJEODlB
NDRDRjM3M0U3RUU5OUU0AAoJEKRM83Pn7pnkBGkQALzb+HSsWSfKVmtMKD5mioIl
tIQHjyR9WOARTBCv7QRfBTfUPtMXo+1aY8xX72eOtZ3UTDXy6ieaCjKJn25tDP1z
u9rw4r3ClPsE+vBcQjg6fAJLeBIawJkEhGQxWFQQMxwnG1Trg7UjicJJuy+AmfKZ
WIqUFtNVuNPXTcHlQax8c5gWN1hM7Q4GgPiqzhQZ8/YDVnnxAvC4VZZTQUCffr8T
Q+rE/DYOFkusUkWrsUXcokgFwwggJitbsKhImKivdB2H/+nQrstXGoFsyl4kU6gD
i3UCeFiNx+zchYF+XtnKOfxtYS5gNjMZsdKEJUktVV+dV7Xg5Fqpbh8HzEf2hzlj
rY4fqLuBvR5ypJqwG1DeRDhMifaM4Xa/dAe93O1DFtXtO64onIwGZI+FKFdEyRT9
GcBjzWv+/iLRBQ+vafh6AO9dzJ5gpDW7BxOJp3v4CSqqDlAPv5GG7lwDGXlN9Y7j
XD42ks8UUFpu3eMikFcrlR6vqT3aGclu/H2jaA9WvfAE7BdpY/MjkEJkgCedxf3Q
W7aY95NvmyN0MHJLfRQG/ZwZr7aDUCPj5H/ECyZlhIcvbS7FqV65LRI62pyy0Rfj
/sIaiSEmdyzdAtw5CPF+0D74AG3mFE7/92ptAQFwCVicIEObHPy084fXDmYKhgK+
cZz+90PBBcYBDRslcQ8a
=O//d
-END PGP SIGNATURE-

[gentoo-dev] Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14

[Dirkjan Ochtman]

On Tue, Feb 2, 2016 at 3:18 PM, Justin Lecher (jlec)  wrote:
> Could you please sum up the thread and come up with some precise
> question we should discuss or vote on.

The question is: what language should we use for XML validation in the future?

There are two main contenders: RELAX NG (with a compact and an XML
serialization) and XML Schema. Of course conversion between these
schema formats is possible, but the question is what the canonical
language should be and what other formats would be provided (and how).

Summary:

- I contended that RELAX NG compact serialization is more readable,
and that DTD and RELAX NG validation are equally fast. I don't have
much experience with XML Schema, but I do have a conversion tool for
RNC (compact RELAX NG) -> RNG (RELAX NG XML syntax).
- Michał has used both RELAX NG and XML Schema, and prefers the
latter. It's more popular, and it seems that cross-referencing things
is not supported (trivially) in RELAX NG, whereas it should be in XML
Schema.
- Robin prefers XML Schema, but can live with both.
- trang seems to be a pretty decent tool for schema conversion, but it
doesn't handle XML Schema as an input language (likely because of the
complexity of XML Schema).
- There is a standard for referring to RELAX NG or XML Schema schemas
from XML documents, which would be useful for tool authors.
- emacs nXML mode works only with RNC schema, which is a reason for
Ulrich to prefer it.
- Brian seems to like RNC for readability/flexibility reasons.

I hope other will jump in if they feel I missed
something/misrepresented their opinions.

Cheers,

Dirkjan

Re: [gentoo-dev] abusive behaviour / communications from a user

[Jeroen Roovers]

On Tue, 2 Feb 2016 11:14:20 +0800
Ian Delaney  wrote:

> Members of comrel

[...]

> Please consider this and assess as you see fit.

kthx


 jer

Re: [gentoo-dev] Re: [PATCH 0/5] RFC: Patches for wxwidgets.eclass

[Justin Lecher (jlec)]

On 02/02/16 23:36, Ryan Hill wrote:
> On Mon,  1 Feb 2016 12:08:28 +0100
> Justin Lecher  wrote:
> 
>> while tracking down the following error when running "egencache"
>>
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>> GENTOO.GIT//eclass/wxwidgets.eclass: line 84: get_libdir: command not found
>>
>> I found that the global scope get_libdir() usage of the wxwidgets.eclass
>> doens't work on EAPI=6. The following patches correct some minor things
>> and block EAPI=6 for now until the eclass is ready.
>>
>> Justin Lecher (5):
>>   wxwidgets.eclass: Update Copyright year
>>   wxwidgets.eclass: Fix whitespaces
>>   wxwidgets.eclass: unset unneeded variables in global scope after usage
>>   wxwidgets.eclass: Only inherit eclass ones
>>   wxwidgets.eclass: Add EAPI support
>>
>>  eclass/wxwidgets.eclass | 33 -
>>  1 file changed, 24 insertions(+), 9 deletions(-)
>>
> 
> 1. I don't think most of this is necessary but go ahead I guess.

Most of them are trivial, but excluding EAPI=6 from supported EAPIs is
essential. The usage of get_libdir needs to be moved to a phase
function. Which should perhaps be coupled with an env variable which is
checked in the later function to ensure the phase function has been run.

> 2. When did we start posting every @&#$! eclass change to g-dev?  File a bug
> like a normal person.  (There's already one open you could have used)

I feel pretty "normal" when sending eclass changes to g-dev. Having code
reviewed which influences a larger number of packages at once in the
most public and open way is something we should strive for, isn't it?



signature.asc
Description: OpenPGP digital signature