Roy Marples wrote:
On Tue, 2007-10-16 at 13:38 +0100, Steve Long wrote:
Roy Marples wrote:
On Tue, 2007-10-16 at 00:28 -0700, Donnie Berkholz wrote:
On 08:19 Tue 16 Oct , Steve Long wrote:
stdDocs=(ChangeLog AUTHORS FEATURES THANKS README CodingStyle TODO
FAQ)
stdDoc() {
Hanno Böck a écrit :
Hi,
I'm currently working on ebuilds for openvas (free successor of nessus). Now
something nags me, I get a QA warning I'm not able to fix:
net-analyzer:openvas-libraries-1.0.0:20071013-001835.log- * hg_dns_axfr.c:85:
warning: implicit declaration of function
On Wed, 2007-10-17 at 10:52 +0200, Hanno Böck wrote:
net-analyzer:openvas-libraries-1.0.0:20071013-001835.log- * hg_dns_axfr.c:85:
warning: implicit declaration of function '_getshort'
The function _getshort is part of glibc, but it's nowhere referenced in the
headers. It probably should
On Wed, 2007-10-17 at 10:15 +0100, Steve Long wrote:
OK, that's all good, and you're _right_ for this case. I guess I was trying
to show an array being used since it came up before. For instance, I often
add to a global array with eg failed+=($1), which I might display
one-per-line to the user
Hello List
The BSD team is starting to get a touch irritated by the constant
dropping of elibtoolize from ebuilds. We need this so that we get
nice .so version numbers as well as to fix a few libtool issues on the
BSD platforms.
Just because it's there doesn't mean it's safe to remove as it
Roy Marples [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted below, on
Wed, 17 Oct 2007 15:54:36 +0100:
Basically, if it has a fbsd keyword don't drop elibtoolize without
querying us first.
What about putting it in an fbsd conditional? That way Linux users don't
have to deal with the
I don't normally ask devs for extra testing, but one set of packages
hasn't been responsive to my other requests for testing (I do use it
myself, but I'd like more testing), and I'd like it to be ready before
the next release because of two past bugs that I don't want to exist in
the 2007.1 media.
On 19:51 Wed 17 Oct , Duncan wrote:
What about putting it in an fbsd conditional? That way Linux users don't
have to deal with the step if it's unnecessary for them, while the fbsd
users still get it when they need it. Seems to me this should be a
workable compromise, where people
On Wed, 2007-10-17 at 15:25 -0700, Donnie Berkholz wrote:
On 19:51 Wed 17 Oct , Duncan wrote:
What about putting it in an fbsd conditional? That way Linux users don't
have to deal with the step if it's unnecessary for them, while the fbsd
users still get it when they need it. Seems
Roy Marples kirjoitti:
On Wed, 2007-10-17 at 15:25 -0700, Donnie Berkholz wrote:
On 19:51 Wed 17 Oct , Duncan wrote:
What about putting it in an fbsd conditional? That way Linux users don't
have to deal with the step if it's unnecessary for them, while the fbsd
users still get it when
On 15:55 Wed 17 Oct , Daniel Drake (dsd) wrote:
1.1 sys-apps/sandbox/sandbox-1.2.18.1-r1.ebuild
file :
http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/sandbox/sandbox-1.2.18.1-r1.ebuild?rev=1.1view=markup
plain:
Roy Marples wrote:
On Wed, 2007-10-17 at 10:15 +0100, Steve Long wrote:
OK, that's all good, and you're _right_ for this case. I guess I was
trying to show an array being used since it came up before. For instance,
I often add to a global array with eg failed+=($1), which I might
display
Donnie Berkholz wrote:
On 15:55 Wed 17 Oct , Daniel Drake (dsd) wrote:
1.1 sys-apps/sandbox/sandbox-1.2.18.1-r1.ebuild
file :
http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/sandbox/sandbox-1.2.18.1-r1.ebuild?rev=1.1view=markup
plain:
On 10/17/07, Doug Goldstein [EMAIL PROTECTED] wrote:
Donnie Berkholz wrote:
On 15:55 Wed 17 Oct , Daniel Drake (dsd) wrote:
1.1 sys-apps/sandbox/sandbox-1.2.18.1-r1.ebuild
file :
14 matches
Mail list logo
