Re: [gentoo-dev] dev-lang/v8 SONAME
* "Paweł Hajdan, Jr." (phajdan...@gentoo.org) wrote: > I'm curious: do you have some more ebuilds using v8? It'd be great to > add them to the portage tree at some point, if possible. Or maybe > sunrise overlay... We took the easy way out and chose Debian because v8/nodejs were packaged when we needed them, but we'd prefer to be using Gentoo. That is the reason I jumped straight in when I saw the mail subject. Thanks, James pgpFTKpE0SVMK.pgp Description: PGP signature
Re: [gentoo-dev] dev-lang/v8 SONAME
* "Paweł Hajdan, Jr." (phajdan...@gentoo.org) wrote: > There is one issue that keeps dev-lang/v8 in hard mask and prevents its > broader usage (I think www-client/chromium could start using it). Thanks for working on this. I use v8 quite a bit, and being able to simply depend on the ebuilds would make life easier. One question: Are the v8 ebuilds going to be switched to use some kind of snapshot tarballs before they're unmasked? Thanks, James pgpg3mKijBG2M.pgp Description: PGP signature
Re: [gentoo-dev] start-stop-daemon and python-wrapper
Excerpts from Brian Harring's message of Fri Dec 18 20:16:19 + 2009:
> On Tue, Dec 15, 2009 at 03:54:53PM +0700, Max Arnold wrote:
> > Initially my script has "/usr/bin/env python" shebang line. When I checked
> > actual installed
> > file, it contained "/usr/bin/python2.6". Who is responsible for this
> > modification (eclass,
> > distutils or something else)? Why not "/usr/bin/env python2.6"?
>
> distutils. If you find a knob to disable that, I'd be interested...
> ~brian
There isn't a trigger to change this behaviour [currently].
You can monkey patch it quite easily though, if you're willing. Something
like the following pasted in to the setup.py does the trick.
import re
from distutils.command import build_scripts
build_scripts.first_line_re = re.compile("^never gonna match you up$")
--
Thanks,
James
signature.asc
Description: PGP signature
Re: [gentoo-dev] Re: EAPI 3 PMS Draft
* Marijn Schouten (hkBst) (hk...@gentoo.org) wrote: > James Rowe wrote: > > Package tests will have been run a -- possibly large -- number of > > times when users see them if they are rolled in to the EAPI bump. This > > isn't like the current situation of enabling tests and hoping somebody > > has run them during testing. > > You conclusion that developers do not run tests is based on nothing. Using > RESTRICT=test is not a fix and just hides the problem, so it is not > unthinkable > that packages with failing tests get to stable. Well, I didn't suggest using RESTRICT=test so I'm not sure I understand your point. That being said while it definitely isn't a good result that packages with failing tests have RESTRICT=test set those packages aren't going to cause test failures for stable users anyway. Thanks, James 1. http://bugs.gentoo.org/show_bug.cgi?id=85901 pgpzUTzTmUePl.pgp Description: PGP signature
Re: [gentoo-dev] Re: EAPI 3 PMS Draft
* Christian Faulhammer (fa...@gentoo.org) wrote: > Some years ago as a Gentoo beginner I read the documentation of > FEATURES and enabled "test", because it sounded useful. After one week > I disabled it again as merges took too long and some failures occured. > Read: As a normal user I don't want src_test for every single package > that is installed on my system for whatever reason. FEATURES=test is > perfect for people who help maintain the distribution or want to test a > specific subset of packages they heavily rely on. I'm just a user and I run with FEATURES=test, and have done since at least March 2005[1]. I've definitely toyed with disabling it myself, but only because developers aren't using it, which means I catch bugs[2] that would have never existed if the developer had `test' enabled. > So imposing that penalty on everyone even the unexperienced will > likely confuse some people. Go to the forums or the support mailing > list to see what I mean. Package tests will have been run a -- possibly large -- number of times when users see them if they are rolled in to the EAPI bump. This isn't like the current situation of enabling tests and hoping somebody has run them during testing. Thanks, James 1. http://bugs.gentoo.org/show_bug.cgi?id=85901 2. http://bugs.gentoo.org/show_bug.cgi?id=138415 pgpf6HxovZzWP.pgp Description: PGP signature
Re: [gentoo-dev] gentoo-commits list lives!
* Mike Frysinger ([EMAIL PROTECTED]) wrote:
> On Friday 07 September 2007, Alec Warner wrote:
> > On 9/7/07, Doug Goldstein <[EMAIL PROTECTED]> wrote:
> > > Sure... be fancy with all your xsl and xml crap. LONG LIVE THE BRUTE
> > > FORCE PARSE WITH SED!
> >
> > People who parse xml with sed make me cry.
> >
> > grep = also bad.
>
> i'd parse it with xmlgawk if i hadnt punted it from gawk sometime ago
> -mike
app-text/xml2 makes a surprisingly nice replacement for xmlgawk for
people who know not to use sed or awk on XML, yet still want to. For
example:
$ xml2 < /var/lib/repos/gentoo/sys-apps/busybox/metadata.xml \
| awk -F= '/\/herd=/ {print $2}'
embedded
$ xml2 < /var/lib/repos/gentoo/www-client/surfraw/metadata.xml \
| sed '/\/maintainer\/email=/!d;s,^.*=,,'
[EMAIL PROTECTED]
[EMAIL PROTECTED]
or to match Vapier's output just collapse the output:
$ echo $(xml2 < /var/lib/repos/gentoo/www-client/surfraw/metadata.xml \
| awk -F '/\/maintainer\/email=/ {print $2}')
[EMAIL PROTECTED] [EMAIL PROTECTED]
The above examples will cope with cases that will break the simple sed
version, such as "\ndata\n". But then again so does
Vapier's xsltproc solution.
As a hint for other tasks the package can cope with tagsoup too if
called with html2, and it can reassemble with 2xml/2html. There is some
documentation online at the author's website, but its usage is obvious.
Thanks,
James
pgpBdXSAzSX3x.pgp
Description: PGP signature
