[gentoo-dev] [PATCH] ebuild-writing/variables: add a section to explain the ROOT variable #144332

The text is originally based on the patch provided by Thilo Bangert in the bug. It is revised and expanded to mention the use of ROOT in cross-compiling environments as explained in PMS Table 11.1. Gentoo-Bug: https://bugs.gentoo.org/144332 Signed-off-by: Göktürk Yüksek

Re: [gentoo-portage-dev] [PATCH] isolated-functions.sh: eliminate loop in has()

On 4/22/16 9:07 AM, rindeal wrote: >>From edc6df44de4e0f22322062c7c7e1b973bd89f4cd Mon Sep 17 00:00:00 2001 > From: Jan Chren > Date: Fri, 22 Apr 2016 14:21:08 +0200 > Subject: [PATCH] isolated-functions.sh: eliminate loop in has() > > Looping is slow and clutters debug

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On 15/05/16 02:04, Rich Freeman wrote: > On Sat, May 14, 2016 at 8:23 PM, Aaron Bauman wrote: >> On Sunday, May 15, 2016 12:48:12 AM JST Ciaran McCreesh wrote: >>> On Sun, 15 May 2016 08:40:39 +0900 >>> >>> Aaron Bauman wrote: Please enlighten me as to what

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On 15/05/16 01:59, Rich Freeman wrote: > On Sat, May 14, 2016 at 7:40 PM, Aaron Bauman wrote: >> Please enlighten me as to what was impolite here? The strong language of >> "seriously" or definitively stating that the individual did not perform the >> necessary QA actions before

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, May 14, 2016 at 8:23 PM, Aaron Bauman wrote: > On Sunday, May 15, 2016 12:48:12 AM JST Ciaran McCreesh wrote: >> On Sun, 15 May 2016 08:40:39 +0900 >> >> Aaron Bauman wrote: >> > Please enlighten me as to what was impolite here? The strong >> > language

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, May 14, 2016 at 7:40 PM, Aaron Bauman wrote: > > Please enlighten me as to what was impolite here? The strong language of > "seriously" or definitively stating that the individual did not perform the > necessary QA actions before committing? He actually didn't "state"

[gentoo-dev] [PATCH v2 2/4] ebuild-writing/misc-files/metadata: rewrite the section per GLEP 67 #572144

A major rewrite of the section. Here is a brief summary of changes: - Remove the information about the tag per GLEP 67 - Restructure the section in the following order: - metadata.xml syntax - package metadata - metadata examples - maintainer-needed - category metadata - Update the

[gentoo-dev] [PATCH v2 3/4] ebuild-writing/misc-files/metadata: update wrt slotting and per GLEP 68

Add information about specifying slots and subslots in the metadata. Also, update the section according to the specifications in GLEP 68, clarify some of the tags better, and reorder the tags to improve the flow of the text. Signed-off-by: Göktürk Yüksek ---

[gentoo-dev] [PATCH v2 4/4] ebuild-writing/misc-files/metadata: add an example for slots and subslots

Signed-off-by: Göktürk Yüksek --- ebuild-writing/misc-files/metadata/text.xml | 50 + 1 file changed, 50 insertions(+) diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml index

[gentoo-dev] [PATCH v2 1/4] general-concepts/herds-and-projects: update per GLEP 67 #572144 #549490

The changes are: - Rename the title to "Projects and Herds" to put the emphasis on projects - Explain projects and subprojects in a new "Projects" section - Add a subsection for starting new projects - Add a subsection for joining/leaving a project - Put a warning label at the beginning of the

[gentoo-dev] [PATCH v2 0/4] devmanual: update the docs per GLEP 67 and 68

This is the second iteration of the GLEP 67 and GLEP 68 combined changeset. It also adds documentation about slotting in metadata.xml. The changes compared to the previous iteration are: - GLEP 34 reference removed as suggested by ulm - The proper term "slot dependency specifier" is used

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sunday, May 15, 2016 12:48:12 AM JST Ciaran McCreesh wrote: > On Sun, 15 May 2016 08:40:39 +0900 > > Aaron Bauman wrote: > > Please enlighten me as to what was impolite here? The strong > > language of "seriously" or definitively stating that the individual > > did not

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sun, 15 May 2016 08:40:39 +0900 Aaron Bauman wrote: > Please enlighten me as to what was impolite here? The strong > language of "seriously" or definitively stating that the individual > did not perform the necessary QA actions before committing? Both of > which are

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Saturday, May 14, 2016 9:54:11 AM JST Rich Freeman wrote: > On Sat, May 14, 2016 at 7:55 AM, Aaron Bauman wrote: > > On Friday, May 13, 2016 4:52:09 PM JST Ian Delaney wrote: > >> On Sat, 7 May 2016 23:25:58 +0200 > >> > >> Michał Górny wrote: > >> > Do

Re: [gentoo-dev] [PATCH] ebuild-writing/variables: better describe ROOT

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Mike Gilbert: > The current description of ROOT makes no sense and just confuses > people. The new description is paraphrased from PMS. --- > ebuild-writing/variables/text.xml | 5 +++-- 1 file changed, 3 > insertions(+), 2 deletions(-) > > diff

Re: [gentoo-dev] News Item: LastPass package migration

Andrew Udvare: > On 08/05/16 16:56, Andrew Udvare wrote: >> On 07/05/16 22:25, Göktürk Yüksek wrote: >>> Users of Chrome/Chromium and Opera browsers need to switch to >>> app-admin/lastpass-binary-features and follow the instructions >>> displayed on the screen after the installation to complete

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, May 14, 2016 at 3:21 PM, M. J. Everitt wrote: > On 14/05/16 18:52, Rich Freeman wrote: >> On Sat, May 14, 2016 at 1:07 PM, landis blackwell >> wrote: >>> No fun allowed >>> >> Are you saying that you don't want people to have fun developing

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Samstag, 14. Mai 2016, 18:59:02 schrieb M. J. Everitt: > > I think the time is coming, given the diversity of members of this list, > to add tags when we are not describing something > literally. wouldnt a tag be sufficient? - -- Andreas

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On 14/05/16 18:52, Rich Freeman wrote: > On Sat, May 14, 2016 at 1:07 PM, landis blackwell > wrote: >> No fun allowed >> > Are you saying that you don't want people to have fun developing > Gentoo? Or are you trying to say that it is impossible to have fun > developing

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, May 14, 2016 at 1:07 PM, landis blackwell wrote: > No fun allowed > Are you saying that you don't want people to have fun developing Gentoo? Or are you trying to say that it is impossible to have fun developing Gentoo without insulting strangers? I don't

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

No fun allowed On May 14, 2016 12:06 PM, "Rich Freeman" wrote: > On Sat, May 14, 2016 at 12:59 PM, M. J. Everitt > wrote: > > On 14/05/16 17:53, Chí-Thanh Christopher Nguyễn wrote: > >> Gordon Pettey schrieb: > >> > >>> So, it's perfectly okay to make

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On 14/05/16 18:06, Rich Freeman wrote: > > While this is certainly sensible, the irony here is that this whole > discussion was started by somebody making a sarcastic remark when > simply pointing out a mistake would have been just as functional. > > Nobody thinks it is ok to commit broken code.

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, May 14, 2016 at 12:59 PM, M. J. Everitt wrote: > On 14/05/16 17:53, Chí-Thanh Christopher Nguyễn wrote: >> Gordon Pettey schrieb: >> >>> So, it's perfectly okay to make direct commits of obviously broken >>> code that >>> has no chance of working, because community

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On 14/05/16 17:53, Chí-Thanh Christopher Nguyễn wrote: > Gordon Pettey schrieb: > >> So, it's perfectly okay to make direct commits of obviously broken >> code that >> has no chance of working, because community something mumble... > > You may have missed some sarcasm in the post which you replied

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

Gordon Pettey schrieb: So, it's perfectly okay to make direct commits of obviously broken code that has no chance of working, because community something mumble... You may have missed some sarcasm in the post which you replied to. Plus, I don't think anybody said or implied that committing

Re: [gentoo-dev] USE flag proposal: memcached

On 05/14/2016 10:19 AM, Dirkjan Ochtman wrote: > All, > > I want to add a "memcached" USE flag to mail-filters/rmilter. Before > doing so, I looked if there was a global USE flag. There is not, but I > though see usage across 14 packages: > > dev-db/pgpool2[memcached]: Use memcached for query

[gentoo-dev][PATCH v1] sys-devel/libtool: add m4/libtool.m4 patch for ppc64le #581314

Reference Bug: Gentoo Bug: https://bugs.gentoo.org/show_bug.cgi?id=581314 GNU Bug: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348 * m4/libtool (LD=elf64lppc): add recognise definition with CHOST=powerpc64le-unknown-linux-gnu on ppc64le platform and CHOST=powerpc64-unknown-linux-gnu on ppc64

Re: [gentoo-dev] USE flag proposal: memcached

On Sat, 14 May 2016 11:32:02 -0400 "Anthony G. Basile" wrote: > On 5/14/16 11:19 AM, Dirkjan Ochtman wrote: > > All, > > > > I want to add a "memcached" USE flag to mail-filters/rmilter. Before > > doing so, I looked if there was a global USE flag. There is not, > > but I

Re: [gentoo-dev] USE flag proposal: memcached

On 5/14/16 11:19 AM, Dirkjan Ochtman wrote: > All, > > I want to add a "memcached" USE flag to mail-filters/rmilter. Before > doing so, I looked if there was a global USE flag. There is not, but I > though see usage across 14 packages: > > dev-db/pgpool2[memcached]: Use memcached for query

[gentoo-dev] USE flag proposal: memcached

All, I want to add a "memcached" USE flag to mail-filters/rmilter. Before doing so, I looked if there was a global USE flag. There is not, but I though see usage across 14 packages: dev-db/pgpool2[memcached]: Use memcached for query caching dev-php/pecl-mysqlnd_qc[memcached]: Use

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, May 14, 2016 at 6:35 AM, Ciaran McCreesh < ciaran.mccre...@googlemail.com> wrote: > Why? Gentoo is about the community. Requiring a basic standard of commit > quality a) reduces the number of community members who are able to > contribute, 2) leads to fewer forums posts discussing how to

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, May 14, 2016 at 7:55 AM, Aaron Bauman wrote: > On Friday, May 13, 2016 4:52:09 PM JST Ian Delaney wrote: >> On Sat, 7 May 2016 23:25:58 +0200 >> Michał Górny wrote: >> > >> > Do you seriously expect this code to work? How about testing? Or >> > reading

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Friday, May 13, 2016 4:52:09 PM JST Ian Delaney wrote: > On Sat, 7 May 2016 23:25:58 +0200 > Michał Górny wrote: > > > > Do you seriously expect this code to work? How about testing? Or > > reading diffs before committing? > > Absolutely nothing wrong was said here.

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On 14/05/16 12:35, Ciaran McCreesh wrote: > On Sat, 14 May 2016 11:55:42 +0200 >> Am Freitag, 13. Mai 2016, 10:52:09 schrieb Ian Delaney: >>> On Sat, 7 May 2016 23:25:58 +0200 Do you seriously expect this code to work? How about testing? Or reading diffs before committing? >>> Do you

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

On Sat, 14 May 2016 11:55:42 +0200 > Am Freitag, 13. Mai 2016, 10:52:09 schrieb Ian Delaney: > > On Sat, 7 May 2016 23:25:58 +0200 > > > Do you seriously expect this code to work? How about testing? Or > > > reading diffs before committing? > > > > Do you seriously expect us to sit and absorb

Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Freitag, 13. Mai 2016, 10:52:09 schrieb Ian Delaney: > On Sat, 7 May 2016 23:25:58 +0200 > > > > Do you seriously expect this code to work? How about testing? Or > > reading diffs before committing? > > Do you seriously expect us to sit and