Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Drake Wyrm
Harald van D??k [EMAIL PROTECTED] wrote: Any is fine, there is no word splitting or wildcard expansion in shell variable assignments. $ foo=bar * baz $ wombat=$foo $ echo $wombat bar somedir somefile baz -- ^ ^ A

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Harald van Dijk
On Fri, Jun 16, 2006 at 11:31:27PM -0700, Drake Wyrm wrote: Harald van D??k [EMAIL PROTECTED] wrote: Any is fine, there is no word splitting or wildcard expansion in shell variable assignments. $ foo=bar * baz $ wombat=$foo $ echo $wombat bar somedir somefile baz The wildcard

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Mike Frysinger
On Saturday 17 June 2006 01:22, Alin Nastac wrote: Thomas Cort wrote: What is the proper quoting style for using epatch? In the tree there are about 3 different styles... epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds epatch ${FILESDIR}/some-fix.patch# used by

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Mike Frysinger
On Saturday 17 June 2006 01:34, Donnie Berkholz wrote: 2) When you set a variable to a string, you should use quotes. dont need them, bash does not expand in setting variables -mike pgpVgd6PjFRxs.pgp Description: PGP signature

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Robin H. Johnson
On Fri, Jun 16, 2006 at 11:02:27PM -0700, Drake Wyrm wrote: Thomas Cort [EMAIL PROTECTED] wrote: What is the proper quoting style for using epatch? In the tree there are about 3 different styles... snip What is the proper quoting style for defining the S variable? In the tree there are

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Kevin F. Quinn
On Sat, 17 Jun 2006 00:30:04 -0700 Robin H. Johnson [EMAIL PROTECTED] wrote: If I have a package that produces a dynamic (non-static) binary, and it has no other deps, then I throw in virtual/libc. If it produces a static binary only, or no binary, then it gets . If you're going to do that,

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Peper
Setting RDEPEND to indicates that the stuff in DEPEND isn't needed to run the package, and can safely be pruned later. If RDEPEND is not set, it is defaulted to $DEPEND by portage. If you inherit some eclass with deps, not set RDEPEND won't be defaulted to DEPEND from ebuild, but will also

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Kevin F. Quinn
On Sat, 17 Jun 2006 03:33:28 -0400 Mike Frysinger [EMAIL PROTECTED] wrote: On Saturday 17 June 2006 02:02, Drake Wyrm wrote: Thomas Cort [EMAIL PROTECTED] wrote: DEPEND=virtual/libc # used by 809 ebuilds There are opinions on both sides of this subject, but I think that most devs

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Drake Wyrm
Harald van D??k [EMAIL PROTECTED] wrote: On Fri, Jun 16, 2006 at 11:31:27PM -0700, Drake Wyrm wrote: Harald van D??k [EMAIL PROTECTED] wrote: Any is fine, there is no word splitting or wildcard expansion in shell variable assignments. $ foo=bar * baz $ wombat=$foo $ echo

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Carsten Lohrke
On Saturday 17 June 2006 14:39, Michael Cummings wrote: Kevin F. Quinn wrote: If RDEPEND is not set, it is defaulted to $DEPEND by portage. Alas, if only. If you inherit an eclass with deps this carry over won't happen. (And I have the bugs to prove it ;) Well, has been the job of the

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-17 Thread Peper
| If you inherit some eclass with deps, not set RDEPEND won't be | defaulted to DEPEND from ebuild, but will also include deps from | eclass, which is incorrect b/c these deps are needed for build time | only(like sed, autotools...). One needs to make sure that RDEPEND is | correct if not set

[gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-16 Thread Thomas Cort
What is the proper quoting style for using epatch? In the tree there are about 3 different styles... epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds epatch ${FILESDIR}/some-fix.patch# used by 3092 ebuilds epatch ${FILESDIR}/some-fix.patch# used by

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-16 Thread Alin Nastac
Thomas Cort wrote: What is the proper quoting style for using epatch? In the tree there are about 3 different styles... epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds epatch ${FILESDIR}/some-fix.patch# used by 3092 ebuilds epatch

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-16 Thread Donnie Berkholz
Thomas Cort wrote: What is the proper quoting style for using epatch? In the tree there are about 3 different styles... epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds epatch ${FILESDIR}/some-fix.patch# used by 3092 ebuilds epatch

Re: [gentoo-dev] variable quoting, setting optional variables to , and depending on virtual/libc

2006-06-16 Thread Harald van Dijk
On Sat, Jun 17, 2006 at 12:35:30AM -0400, Thomas Cort wrote: What is the proper quoting style for using epatch? In the tree there are about 3 different styles... epatch ${FILESDIR}/some-fix.patch # used by 7326 ebuilds epatch ${FILESDIR}/some-fix.patch# used by 3092