[gentoo-dev] Two herds (and four extra?)
This is madness, people. Two herds and four separately mentioned developers? Why don't you join a herd? Go on, it's fun and you don't have to be alone! jer gentoo-x86/sys-kernel/hardened-sources $ cat metadata.xml ?xml version=1.0 encoding=UTF-8? !DOCTYPE pkgmetadata SYSTEM http://www.gentoo.org/dtd/metadata.dtd; pkgmetadata herdkernel/herd herdhardened/herd maintainer emailquantumsumm...@gentoo.org/email nameMatthew Summers/name /maintainer maintainer emailrobb...@gentoo.org/email nameRobin H. Johnson/name /maintainer maintainer emailchain...@gentoo.org/email nameTony Vroon/name /maintainer maintainer emailbluen...@gentoo.org/email nameAnthony G. Basile/name /maintainer [...]
Re: [gentoo-dev] Two herds (and four extra?)
On Wed, 2010-07-21 at 13:34 +0200, Jeroen Roovers wrote: This is madness, people. Two herds and four separately mentioned developers? This is madness. THIS IS HARDENED. Why don't you join a herd? Go on, it's fun and you don't have to be alone! This was originally done because we were bypassing a herd (lead) in getting our updates in. Toning it down is not a problem, would just blueness in the list address your concerns? jer Regards, Tony V. signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Two herds (and four extra?)
On Wed, 21 Jul 2010 13:36:26 +0100 Tony \Chainsaw\ Vroon chain...@gentoo.org wrote: This was originally done because we were bypassing a herd (lead) in getting our updates in. Toning it down is not a problem, would just blueness in the list address your concerns? Current b-w policy is to assign to the first mentioned maintainer, then CC all other maintainers and herds[1], so if blueness has no problem with that, then sure. jer [1] Or why would you mention them separately? I think we should still encourage developers to join herds.
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-util/netbeans: ChangeLog netbeans-6.9-r3.ebuild
On Mon, 19 Jul 2010 20:24:40 + (UTC), Miroslav Sulc (fordfrog)
fordf...@gentoo.org wrote:
fordfrog10/07/19 20:24:40
Modified: ChangeLog netbeans-6.9-r3.ebuild
Log:
netbeans-6.9-r3: added support for including custom patches when
building netbeans
+ # Support for custom patches
+ if [ -n {NETBEANS_PATCHES_DIR} -a -d ${NETBEANS_PATCHES_DIR} ] ;
then
+ local files=`find ${NETBEANS_PATCHES_DIR} -type f`
+
+ if [ -n ${files} ] ; then
+ einfo Applying custom patches:
+
+ for file in ${files} ; do
+ epatch ${file}
+ done
+ fi
+ fi
+
Miroslav, You just reinvented the wheel :) Any reason why epatch_user()
from euitls.eclass doesn't work here?
-Jeremy
Re: [gentoo-dev] Two herds (and four extra?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/21/2010 08:58 AM, Jeroen Roovers wrote: On Wed, 21 Jul 2010 13:36:26 +0100 Tony \Chainsaw\ Vroon chain...@gentoo.org wrote: This was originally done because we were bypassing a herd (lead) in getting our updates in. Toning it down is not a problem, would just blueness in the list address your concerns? Current b-w policy is to assign to the first mentioned maintainer, then CC all other maintainers and herds[1], so if blueness has no problem with that, then sure. jer [1] Or why would you mention them separately? I think we should still encourage developers to join herds. I would prefer the bugs be assigned to hardened-ker...@gentoo.org and cc'ed to harde...@gentoo.org. All relevant devs should be on one or the other list. However, I am currently the principle maintainer of h-s. The reason for my preference is 1) that's how we have been doing it since before my time and that's how we keep track of bugs. See [1] for links to the open hardened-kernel bugs. 2) There is a close relationship between hardened-kernel and hardened. They are not two separate projects. The only reason for the two lists is to help keep the issues straight: kernel issues to hardened-kernel and userland/toolchain issues to hardened. [1] http://dev.gentoo.org/~blueness/hardened-sources/ - -- Anthony G. Basile, Ph.D. Gentoo Developer -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxHB+AACgkQl5yvQNBFVTVK+wCgoA/CQPUwAwiOihjvkL2JfeZq Rh0AoIgEPP8MfrRUNyRSRLcwg2W/quyF =Qhls -END PGP SIGNATURE-
[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-util/netbeans: ChangeLog netbeans-6.9-r3.ebuild
Dne 21.7.2010 16:35, Jeremy Olexa napsal(a):
On Mon, 19 Jul 2010 20:24:40 + (UTC), Miroslav Sulc (fordfrog)
fordf...@gentoo.org wrote:
fordfrog10/07/19 20:24:40
Modified: ChangeLog netbeans-6.9-r3.ebuild
Log:
netbeans-6.9-r3: added support for including custom patches when
building netbeans
+# Support for custom patches
+if [ -n {NETBEANS_PATCHES_DIR} -a -d ${NETBEANS_PATCHES_DIR} ] ;
then
+local files=`find ${NETBEANS_PATCHES_DIR} -type f`
+
+if [ -n ${files} ] ; then
+einfo Applying custom patches:
+
+for file in ${files} ; do
+epatch ${file}
+done
+fi
+fi
+
Miroslav, You just reinvented the wheel :) Any reason why epatch_user()
from euitls.eclass doesn't work here?
-Jeremy
y, i did not expect this function to exist, i only recall that i saw
some custom code for applying patches in some other ebuild few years
back when i needed to tweak some package, so did it the same way.
so this is called automatically for
/etc/portage/patches/category/(PF|P|PN) if i read the code right? i
also tried to search man pages for portage and emerge but there is
nothing about it (or i am blind) ... so this is undocumented feature? i
did not know about this cool feature till now.
m.
Re: [gentoo-dev] Two herds (and four extra?)
On Wed, 21 Jul 2010 10:44:48 -0400 Anthony G. Basile bluen...@gentoo.org wrote: I would prefer the bugs be assigned to hardened-ker...@gentoo.org and cc'ed to harde...@gentoo.org. All relevant devs should be on one or the other list. However, I am currently the principle maintainer of h-s. You really don't expect the currently 5-10 regular bug wranglers to remember all that, do you? If you want things listed in a specific order, then just remember the rules: = Alternative A = * first maintainer from the top down gets to be assignee, * otherwise the first herd gets to be assignee. Put them in the right order an you should have no problem with bug assignments. We could discuss this processing order (maybe change it to having = Alternative B = * the top herd or maintainer as assignee (but I really don't want to get tangled up in a discussion about your preferences or anyone's preferences, and how bug wranglers should reflect those). jer
Re: [gentoo-portage-dev] Google Summer of Code: Bash AST and grammar
On 07/21/10 15:49, Nathan Eloe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello portage developers My name is Nathan Eloe, and I'm working on a Google Summer of Code project in which I'm writing a library that will create an Abstract Syntax Tree of the bash grammar. In essence I am recreating the bash grammar and structuring it as an AST. I am writing to you because you have shown interest in this project. I have attached a bash script which demonstrates the supported functionality of the grammar thus far and the resulting AST. Nice, you have covered quite a few constructs alraedy. I would greatly appreciate input on the tree I'm unsure if such a big file and tree is good to handle. I propose to split this test suite to many small cases. as well as insight into missing functionality you might see. A few things I haven't seen, yet: # Adjacent changes in quotation echo abc''def # Makes abcdef # Escape sequences like .. echo abc\def # Invocation from ibnside strings echo foo $(echo foo), bar `echo bar` # Heredocs (and their variations ..) cat EOF /dev/stdout 1 2 EOF # Construct of $((..)) # Refs to variable withzout $ upfront z=3; echo $((z+3)) Best, Sebastian
Re: [gentoo-portage-dev] Google Summer of Code: Bash AST and grammar
On 07/21/10 16:56, Sebastian Pipping wrote: A few things I haven't seen, yet: # Adjacent changes in quotation echo abc''def # Makes abcdef # Escape sequences like .. echo abc\def # Invocation from ibnside strings echo foo $(echo foo), bar `echo bar` # Heredocs (and their variations ..) cat EOF /dev/stdout 1 2 EOF # Construct of $((..)) # Refs to variable withzout $ upfront z=3; echo $((z+3)) An important one I forgot: # Line continuation echo one \ two Potentially hase quite a few sub cases .. Best, Sebastian
Re: [gentoo-portage-dev] Google Summer of Code: Bash AST and grammar
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/21/10 10:25 AM, Sebastian Pipping wrote: On 07/21/10 16:56, Sebastian Pipping wrote: A few things I haven't seen, yet: # Adjacent changes in quotation echo abc''def # Makes abcdef # Escape sequences like .. echo abc\def # Invocation from ibnside strings echo foo $(echo foo), bar `echo bar` I'll test those, though I think the only one that I haven't even thought about was the escape sequences # Heredocs (and their variations ..) cat EOF /dev/stdout 1 2 EOF Heredocs/strings are... present but broken. The problem is they just consume strings like crazy. Perhaps with some semantic predicates I can get it to stop at the end. For now though it would just keep consuming till the end of the file # Construct of $((..)) # Refs to variable withzout $ upfront z=3; echo $((z+3)) An important one I forgot: # Line continuation echo one \ two Both of these have yet to be implemented, though doing so should be trivial. Thanks for the input! Any and all input I can get is helpful. Nathan -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxHH5MACgkQFpoRlVgtqKbnfwCbBdgYaqZfSLxa7GTgrtV1wZfg e94An3HkOPUE6BVQ1YsyeogJ92ZsRK6z =5ezP -END PGP SIGNATURE-
