Iain Buchanan wrote:
>
> On Thu, 2008-02-28 at 14:28 +0200, Petteri Räty wrote:
>> He has been breaking the tree for a while now but as Calchan has been
>> having availability problems I get to insult him a little bit later than
>> usual. Bo hails from Aalborg, Denmark. He studies to become a con
Fabian Groffen wrote:
> Ben de Groot wrote:
>> Bernd Steinhauser wrote:
>> | Wouldn't it be more clean if it is amd64 just like the Linux one?
>> | Because the arch basically is the same. I think that
>> | amd64(-linux) -- x86_64-fbsd
>> | x86(-linux) -- x86-fbsd
>> |
>> | would be more confusing t
Felipe Contreras wrote:
> On Sat, Feb 23, 2008 at 10:45 PM, Alec Warner <[EMAIL PROTECTED]> wrote:
>> On 2/20/08, Felipe Contreras <[EMAIL PROTECTED]> wrote:
>> > b) Error are difficult to handle since bash doesn't have exceptions
>>
>> I disagree here: most errors are fatal anyway any non fata
Oleg Puchinin wrote:
> Hello!
> I develop project SilentBob ( http://silentbob.sf.net ).
> I would like to see SilentBob in Gentoo.
> Somebody can help me with it?
>
> Oleg.
Bug as mentioned, #gentoo-dev-help #bash and ##workingset on
irc.freenode.org for help, then once it's maintainer-wanted,
Peter Volkov wrote:
> ? ???, 13/02/2008 ? 21:38 +0100, Markus Meier ?:
>> On Wed, 13 Feb 2008 21:13:09 +0100
>> [EMAIL PROTECTED] (Diego 'Flameeyes' Pettenò) wrote:
>> > > css: Enables ripping of encrypted DVDs
>> >
>> > Are we sure that nothing intends css as Cascading Style Sheet?
>>
>> ap
Ryan Hill wrote:
> Donnie Berkholz wrote:
>> On 12:15 Mon 21 Jan , Jean-Noel Rivasseau (elvanor) wrote:
>>> # No warnings / Java 5 / all output should be directed to stdout
>>> find "${S}" -type f -name '*.xml' -exec \
>>> sed -r -e "s:(-encoding ISO-8859-1):\1 -nowarn:g" -e "s:(\"compilerArg\
Ferris McCormick wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This is random musing based based on perhaps my own problems.
> I need a local color.file to see well what I have going on, and
> current xorg ignores that. Thus, at every build, there is in
> oscolor.c a "constant"
Joe Peterson wrote:
> On Thu, Jan 17, 2008 at 10:56:36AM +0000, Steve Long wrote:
>> Ryan Hill wrote:
>>> I agree, though year of birth might be interesting. Income and children
>>> are a bit too private.
>>>
>> ++ in general although I do think parent
Robin H. Johnson wrote:
> On Thu, Jan 17, 2008 at 10:56:36AM +0000, Steve Long wrote:
>> Ryan Hill wrote:
>> > I agree, though year of birth might be interesting. Income and
>> > children are a bit too private.
>> >
>> ++ in general although I
Ryan Hill wrote:
> I agree, though year of birth might be interesting. Income and children
> are a bit too private.
>
++ in general although I do think parenthood (if responsible) is as relevant
as age. A 28 year old with a 5 year old kid has a lot to show a 35 year old
doctoral student with no k
Samuli Suominen wrote:
> Since dostrow is being retired or is retired, correct me if I'm wrong
> we decided (actually we rolled dices :-) that welp is the new lead.
>
Congrats welp! :D
Can I have my `lucky' dice back now? ;P
--
gentoo-dev@lists.gentoo.org mailing list
Chrissy Fullam wrote:
>> Ferris McCormick wrote:
>> With all due respect, for some reason we don't have Proctors
>> anymore to enforce the CoC. Thus, things we would expect the
>> proctors to catch and handle under CoC get sent to devrel
>> instead. All I am doing is wondering out loud (now that
Santiago M. Mola wrote:
> On Jan 3, 2008 11:40 AM, Roy Marples <[EMAIL PROTECTED]> wrote:
>> On Thu, 2008-01-03 at 10:18 +, Richard Brown wrote:
>> > While this thread remains highly entertaining, I'm sure as a past
>> > gentoo developer Roy remembers that we don't generally use gentoo-dev
>>
Roy Marples wrote:
> So, the question is, do we want to maintain one massive KV_to_int that
> has different code paths for uname -s output, or get function.sh to
> include an OS specific file we supply just for this one function?
>
> Or just put the function in modules-update and udev as they are
Luca Barbato wrote:
> Some items I have in wishlist
>
> - LRDEPEND link runtime dep (I need to link against that in order to run)
I heartily concur with a link dependency, since it's such a fundamental
relationship between packages: if A links to B we need to recompile A when
the ABI for B chang
Ciaran McCreesh wrote:
> On Fri, 28 Dec 2007 05:21:06 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> Whatever. EAPI="2" works fine with current software. Could you tell
>> me why you're so hot on export'ing EAPI? I thought it was only
>> relev
Chris Gianelloni wrote:
>> branding: Enable Gentoo specific branding
>> [questionable, as used for splashes/shortcuts/artwork]
>
> Well, my personal opinion here is that we should enable this by default
> on *at least* the desktop profiles, as providing sensible defaults and
> branding isn't outs
another contrived b0rkage. You really don't have a very high
opinion of Gentoo devs, do you?
> EAPI="1"
> export EAPI=2
>
> src_compile() {
> cat < somefile
> EAPI=3
> END
> }
>
All those would be dealt with by the well-defined syntax. I'd s
Ciaran McCreesh wrote:
> On Mon, 24 Dec 2007 10:52:53 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> Ciaran McCreesh wrote:
>> > On Mon, 24 Dec 2007 06:03:12 +
>> > Steve Long <[EMAIL PROTECTED]> wrote:
>> >> * Set the EAPI inside th
Ciaran McCreesh wrote:
> On Fri, 21 Dec 2007 14:29:25 +0100
>> The majority of devs don't want to know how portage or paludis work
>> internally, that's not what interests most of us.
>
> Which is fine. But then, the majority of devs shouldn't expect to be
> able to provide opinions when it comes
Ciaran McCreesh wrote:
> On Mon, 24 Dec 2007 06:03:12 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> * Set the EAPI inside the ebuild in a way that makes it easy to
>> fetch it This is ok as atm only EAPI=1 is in the tree, so there is no
>> backward compati
Piotr Jaroszy?ski wrote:
> Hello,
>
> I have updated the GLEP, hopefully it is less confusing now and hence the
> discussion will be more technical.
>
Based on your summary of the suggestions on the list, I believe you
misunderstood what many of us were arguing for.
* Set the EAPI inside the e
Carsten Lohrke wrote:
> On Mittwoch, 12. Dezember 2007, Ciaran McCreesh wrote:
>> * Eclasses may not set EAPI.
>>
>> * Eclasses may not assume a particular EAPI.
>
> I disagree here. It would be annoying and possibly even hindering in
> future not being able to use higher EAPI features in eclasses
Denis Dupeyron wrote:
> Richard is married and has two children.
Yay a parent! (How many are there? I can only think of Neddy..)
> So please everybody, give a warm welcome to Richard.
>
Well done Rich :D
--
[EMAIL PROTECTED] mailing list
Duncan wrote:
> Steve Long <[EMAIL PROTECTED]> posted
> [EMAIL PROTECTED], excerpted below, on Sat, 22 Dec 2007 06:35:07
> +:
>
>> Oh yeah I forgot, McCreesh thinks they're all idiots[1], so let's just
>> do what he says.
>
>> [1]
>> ht
Piotr Jaroszy?ski wrote:
> On Saturday 22 of December 2007 02:41:02 Petteri Räty wrote:
>> Piotr Jaroszy?ski kirjoitti:
>> > This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds
>> > (for example, foo-1.2.3.ebuild-1).
>>
>> It seems many people don't like the idea of having it in
Duncan wrote:
> our users -- Gentoo sysadmins by another name.
THANK YOU! Finally someone said it (and explained it better than I could.)
All our users-- the ones who deal with the glitches that can arise in a
source distro which binary users never see-- have the skill level of an
admin anywhere
Bo Ørsted Andresen wrote:
> On Friday 21 December 2007 03:41:04 Luca Barbato wrote:
>> > * We have to wait a year before we can use it.
>>
>> We have to wait till we got a new release and I hope it isn't 12months.
>
> And then we have to wait till noone use a version of portage that sources
> the
Ciaran McCreesh wrote:
> On Thu, 20 Dec 2007 12:48:31 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> >> No: without knowing the EAPI when generating said data. If that
>> >> needs to be known relatively soon in order to generate the rest,
>> >> e
Ciaran McCreesh wrote:
> On Thu, 20 Dec 2007 00:07:35 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> Do you think a generated EAPI is a good idea? I'm curious as to
>> how that would be reflected in the filename (as well as your reasons
>> ofc.)
>
>
Ciaran McCreesh wrote:
>> >> Are you really telling me you are going to write _one_ ebuild
>> >> with /that/ god-awful hackery in it?
>> >
>> > Are you really suggesting that no-one ever will?
>> >
>> They won't if the spec and the docs say it's restricted to a single
>> instance, which can be che
Ciaran McCreesh wrote:
> On Wed, 19 Dec 2007 10:26:16 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> Are you really telling me you are going to write _one_ ebuild
>> with /that/ god-awful hackery in it?
>
> Are you really suggesting that no-one ever will?
>
Th
Fernando J. Pereda wrote:
>> > Why can't it be in the file but readable without sourcing?
>> >
>> There's _no_ need to source, nor constrain like that, for a simple
>> one-line variable, eg:
>> $ sed -nr '/^[[:space:]]*DESCRIPTION="([^"]*)".*/ { s//\1/p;q; }' \
>> app-portage/autounmask/autoun
Thomas de Grenier de Latour wrote:
> On 2007/12/18, Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
>
>> On Mon, 17 Dec 2007 17:10:46 -0700
>> Joe Peterson <[EMAIL PROTECTED]> wrote:
>> > I probably missed some of the stuff leading up to this GLEP, but
>> > what is the problem with having the EAPI in
Duncan wrote:
> Donnie Berkholz <[EMAIL PROTECTED]> posted
> [EMAIL PROTECTED], excerpted below, on Sun, 16 Dec 2007
> 12:49:13 -0800:
>
>> I think it's valuable to show the flags that actually need to be changed
>> rather than a full list of all required flags.
>
> ++
>
I messed about on some
Mike Frysinger wrote:
>> Personally I prefer using embedded multiline echo:
>> echo '
>> CONFIG_FOO
>> CONFIG_BAR
>> CONFIG_BLAH
>> ' >> "$CONFIG"
>
> the point of using cat with <<- is so that it wont look like crap when you
> put
> it into the ebuild. you can use normal tab indentation. an ech
Peter Volkov wrote:
> ? ???, 13/12/2007 ? 10:52 +0000, Steve Long ?:
>> Peter Volkov wrote:
>> > Speaking about the
>> > latter it is:
>> >
>> > 1. Modify eclass to use arrays:
>> >
>> > for conffile in [EMAIL PROTECTED]; d
Mike Frysinger wrote:
> On Tuesday 11 December 2007, Denis Dupeyron wrote:
>> On Dec 11, 2007 6:03 AM, Mike Frysinger <[EMAIL PROTECTED]> wrote:
>> > On Monday 10 December 2007, Donnie Berkholz wrote:
>> > > {
>> > > ...
>> > > echo "CONFIG_EAP_SAKE=y"
>> > >
Peter Volkov wrote:
> Thank you all, for your responds.
>
> Currently I see that the best approach is arrays. They provide required
> functionality, clear syntax and easy upgrade path.
++
> Speaking about the
> latter it is:
>
> 1. Modify eclass to use arrays:
>
> for conffile in [EMAIL PROTE
Nirbheek Chauhan wrote:
> On Dec 10, 2007 8:44 PM, Robert Buchholz <[EMAIL PROTECTED]> wrote:
>> That would still mean everything relies on n ebuilds with mutual blocks.
>> Even if that would work and it block upgrades, it is still not a
>> solution in terms of how to display a list of ebuilds in
Petteri Räty wrote:
> Please comment on my ideas in
> http://bugs.gentoo.org/show_bug.cgi?id=201499
>
http://bugs.gentoo.org/attachment.cgi?id=137968&action=view seems to be the
draft spec. I'd like to put in a request for a "link" dependency which is
covered atm by build,target i guess. compile-
Alistair Bush wrote:
> Im sure Elvanor can't wait for you constructive feedback on his eclass
> and depending on your feedback the eclass will enter the tree this
> weekend.
>
A couple of very minor performance points, which I think are more
significant in eclasses. Firstly the basename thing Donni
Duncan wrote:
> "Marijn Schouten (hkBst)" <[EMAIL PROTECTED]> posted
> [EMAIL PROTECTED], excerpted below, on Wed, 28 Nov 2007
> 12:40:58 +0100:
>
>> Donnie Berkholz wrote:
>>> How the recent changes happened to allow USE flag descriptions in
>>> metadata.xml (which I'm not taking any position on
Christian Faulhammer wrote:
> Ciaran McCreesh <[EMAIL PROTECTED]>:
>
>> Is this something worth pinching for a future EAPI? If we go with the
>> postfix [] form for ranged deps, it'd translate into:
>> LICENSE="=GPL-2" (or equivalently, LICENSE="GPL[=2]")
>> LICENSE="|| ( GPL[>=2] BSD )" (
Steve Long wrote:
> No, that's about the size of it-- if you you'd like to tie it to ASCII,
> irrespective of locale, that's fair enough.
>
I had a feeling this statement was incorrect (what zlin said about a-z) so I
asked dalias in #bash who is knowledgeable about locale
Marijn Schouten (hkBst) wrote:
> Duncan Coutts wrote:
>> On Fri, 2007-11-16 at 14:40 +0200, Petteri Räty wrote:
>>> It's my usual please to announce a new ebuild monkey. Justin hails from
>>> Brighton, Massachusetts. His educational background should provide a
>>> good theoretical approach to all t
Jan Kundrát wrote:
> Steve Long wrote:
>>> Is [[:alpha:]] locale-safe?
>>>
>> Yes, all POSIX character classes listed here are:
>> http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html
>
> Thanks for a nice link. If I read section 7.3.1 c
Jan Kundrát wrote:
> Donnie Berkholz wrote:
>>> if [[ -n "${ver}" ]] && [[ ${ver//[a-zA-Z-]} != "${PV//[a-zA-Z]}" ]] ;
>>> then
>>
>> It isn't terribly likely to become an issue here, but it might be nicer
>> to use [[:alpha:]] than [a-zA-Z].
>
> Is [[:alpha:]] locale-safe?
>
Yes, all POSIX char
Ciaran McCreesh wrote:
> On Sun, 11 Nov 2007 09:43:49 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> > Which is just as bad.
>> >
>> No, it's better for the reason given: it doesn't require login as
>> root.
>
> And it's still chec
William L. Thomson Jr. wrote:
> On Sat, 2007-11-10 at 18:36 +0100, Bo Ørsted Andresen wrote:
>> On Sat, Nov 10, 2007 at 11:51:37AM +0100, Krzysiek Pawlik wrote:
>> > It's purpose is to remove the ${D} from makefile, additionally ${D} is
>> > in single quotes, so it will not be expanded - is it a bu
Ciaran McCreesh wrote:
> On Thu, 08 Nov 2007 18:22:48 +
> Steve Long <[EMAIL PROTECTED]> wrote:
>> > if [[ ${UID} -ne 0 ]]; then
>> >
>> > We've always told people not to do that. Capabilities required by
>> > eselect modules should be te
René 'Necoro' Neumann wrote:
> cmake-utils_src_enable python => -DENABLE_python=...
>
> Wanted would be that it returned -DENABLE_PYTHON=...
>
> I'm not into bash scripting that much, so I do not know a way to do so -
> but I guess someone else is ;)
>
Unfortunately BASH doesn't support ksh93 or
Ciaran McCreesh wrote:
> if [[ ${UID} -ne 0 ]]; then
>
> We've always told people not to do that. Capabilities required by
> eselect modules should be tested by attempting to perform the action,
> not by some arbitrary query done on UIDs or groups. Being UID 0 doesn't
> mean you're allowed to do
Jim Ramsay wrote:
> Whether or not 'move' was the correct action in the recent compiz
> example, perhaps we need to consider that some times one package does
> actually make another obsolete. The correct thing for the PM to
> do is to first uninstall the obsolete package, then install the new one.
Alec Warner wrote:
> On 11/4/07, Steve Long <[EMAIL PROTECTED]> wrote:
>> One minor thing; -n is the default test, so:
>> [[ $1 ]] is the same as [[ -n $1 ]]
>> and:
>> [[ ! $1 ]] is the same as [[ -z $1 ]]
>> ''help test'' is very reve
Marijn Schouten (hkBst) wrote:
> the current interface to use flags, useq, usev, use_with, use_enable, as
> defined in /usr/lib/portage/bin/ebuild.sh lacks generality. The common
> thing is testing a use flag and possibly echoing a string, but there is no
> function that implements this common beha
Roy Marples wrote:
> On Sat, 2007-11-03 at 01:19 +0100, Fabian Groffen wrote:
>> Please stop calling it "more portable". The shell code you see in
>> configure can in a way be called "portable". Your POSIX compliant stuff
>> isn't. In fact, by stating #!/bin/sh you actually make the code useles
Alexis Ballier wrote:
> Hi,
>
>> What are we going to do with the global tetex USE flag?
>> app-text/tetex is deprecated in favour of TeXLive which is still hard
>> masked but will be the default TeX distribution in the future.
>> Rename it to tex as TeXLive is based on teTeX? And what about
>> U
Donnie Berkholz wrote:
> On 10:36 Tue 30 Oct , Roy Marples (uberlord) wrote:
>> (find . -name '*.cgi' ; find . -name '*.pl') | perl perlpath.pl
>> /usr/bin/perl -
>
> Please don't tell me the -or find flag isn't POSIX so we can't use it...
>
It's GNU, but why on Earth they saw fit to break scr
Natanael Copa wrote:
> On Sun, 2007-10-28 at 06:46 +0000, Steve Long wrote:
>
>> Failing that, a plaintext config file along the lines discussed in [1]
>> would be cool. awk could parse it pretty quickly.
>>
>> [1] http://modeemi.fi/~tuomov/b//archives/2007/01/20/
Roy Marples wrote:
> I've not opted for another config format (either based on Debians or
> something else) as this doesn't rock the baselayout-2 boat that much as
> it's a fairly trivial patch. Once we have baselayout-2 stable then we
> can think about revisiting this for future versions if there
Roy Marples wrote:
> On Fri, 2007-10-26 at 16:36 +, Duncan wrote:
>> Well, several services already have a "basic" setup using named vars,
>> then something like Richard's suggested Options_eth0= as a (normally
>> commented) catch-all for anything advanced that the admin wishes to pass
>> "raw
Marius Mauch wrote:
> On Sun, 21 Oct 2007 23:13:58 +0100
> Steve Long <[EMAIL PROTECTED]> wrote:
>> Well the line from portage_versions.py is:
>> ver_regexp = re.compile("^(cvs\\.)?(\\d+)((\\.\\d+)*)([a-z]?)((_(pre|
>> p|beta
>> alpha|rc)\\d*)*)(-r(\
Marius Mauch wrote:
> But like name_splitted.cpp is buggy as it assumes that a dash followed
> by a digit starts the version part. See
> echo ${PORTDIR}/*-*/* | tr ' ' '\n' | grep '\-[[:digit:]]'
> for some names that break the assumption.
>
Whoops :S Guess I need to change that then :)
> And n
Markus Rothe wrote:
> Attached are the scripts I use to commit packages stable/unstable.
> Somewhere must be a bug!
>
> 'name_split.cpp' splits a package name like sys-devel/gcc-4.1.2 into
> category, package name and version number. It's done in c++ as that's the
> only language I do more with t
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 e
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 FEATUR
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() {
>> > local d l=()
Thomas de Grenier de Latour wrote:
> On 2007/10/14, Drake Wyrm <[EMAIL PROTECTED]> wrote:
>
>> Or, since you already have the command substitution there, how about:
>>
>> dodoc `find doc -maxdepth 1 -type f`
>
> Or even better, how about explicitly listing the relevant files
> (ChangeLog, AUTHO
Gilles Dartiguelongue wrote:
> I haven't reread the fine mans for a while but iirc, + could lead you to
> hit the argument buffer limit of your shell. xargs has --max-args to get
> around that and is also way faster than any -exec variant (at least
> that's what the bench I did on a PIV2.6Ghz showe
Roy Marples wrote:
> On Mon, 2007-10-15 at 10:43 +0200, Fabian Groffen wrote:
>> On 15-10-2007 09:35:35 +0100, Roy Marples wrote:
>> > find "${D}" -type f -name *${v}.*pm -delete
>>
>> Looks like you rely on your shell here to assume that you meant
>> "*${v}.*pm" because there is nothing that mat
Matti Bickel wrote:
> Steve Long <[EMAIL PROTECTED]> wrote:
>> >> > Mixing 'gt' and 'ge' is a bad idea.
>> >>
>> >> Just outa curiosity, why?
>> >
>> > Because it's inconsistent and one generally assumes
Doug Goldstein wrote:
> I know the other thing I didn't answer was the fact that some variables
> aren't quoted. It doesn't matter at all considering their configure
> script can't handle spaces in the path names anyway. We've been though
> that already. Additionally, qmake can't handle spaces in t
Donnie Berkholz wrote:
> On 23:45 Sat 13 Oct , Drake Wyrm wrote:
>> Donnie Berkholz <[EMAIL PROTECTED]> wrote:
>> > On 13:36 Sat 13 Oct , Matti Bickel (mabi) wrote:
>> > > if kernel_is gt 2 6 20 ; then
>> > > epatch "${FILESDIR}"/${PV}-register_sysctl_table.patch
>> > > fi
>> > >
>> > > if
Donnie Berkholz wrote:
> On 00:12 Sun 14 Oct , Doug Goldstein wrote:
>> Because if you pass the inverse the script blows up. It's ffmpeg's
>> configure script that's a hand written script and modified by the MythTV
>> developers.
>
> Sigh. Any chance of getting things to move to autotools?
>
Zac Medico wrote:
> Steve Long wrote:
>> Is there a cut-off for portage atm wrt versions you do not support?
>>
>> I'm wondering at what point you can say we don't support less than 2.1.2.
>> It seems odd that a distro which operates like Gentoo would not c
Chris Gianelloni wrote:
> On Sat, 2007-10-13 at 10:37 +, Duncan wrote:
>> Chris Gianelloni <[EMAIL PROTECTED]> posted
>> [EMAIL PROTECTED], excerpted below, on Fri,
>> 12 Oct 2007 17:22:54 -0700:
>>
>> > Steve Long wrote:
>
Donnie Berkholz wrote:
> On 18:17 Wed 10 Oct , George Shapovalov (george) wrote:
>> george 07/10/10 18:17:58
>>
>> Modified: gnatbuild.eclass
>>
>> Log: fixed src_install issue, no longer relies on portage leaking
>> env vars between functions
>
> It's really sad that you have to
Duncan wrote:
> Steve Dibb <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
> excerpted below, on Wed, 10 Oct 2007 07:55:01 -0600:
>
>> The reason we have mp3 and lame use flag is because there is more than
>> one mp3 encoder. In almost every case of the use flag being applied
>> above, there is a
Zac Medico wrote:
>> Plus, once we have this, it looks to me that nobody has to wait for
>> EAPI=1 in order to use whatever portage feature that's needed by an
>> ebuild. So we can all stop complaining about not having EAPI=1 in the
>> form we wanted or at all, and get back to writing ebuilds.
>
Natanael Copa wrote:
> On Mon, 2007-10-08 at 20:25 +0100, Steve Long wrote:
>> Natanael Copa wrote:
>
>> If you're that motivated why not just start hacking on binary support in
>> portage/pkgcore/paludis? There's always open bugs.
>
> I think I did co
Natanael Copa wrote:
> On Mon, 2007-10-08 at 06:52 -0700, Alec Warner wrote:
>> On 10/8/07, Natanael Copa <[EMAIL PROTECTED]> wrote:
>> > On Sun, 2007-10-07 at 21:26 -0600, Joe Peterson wrote:
>> > > Mike Frysinger wrote:
>> > > > Fabian has summed it up nicely, thanks. i could care less what
>>
Donnie Berkholz wrote:
> On 13:34 Fri 05 Oct , Steve Long wrote:
>> In actual fact, I'd be more likely to use parameter expansion than set,
>> eg: spec=${CHOST#*-*-} # chop first two fields off so spec is fields 3 on
>> spec=${spec%%-*} # chop all but first off
Roy Marples wrote:
> On Thu, 2007-10-04 at 05:03 +0100, Steve Long wrote:
>> Donnie Berkholz wrote:
>>
>> > spec=$(echo ${CHOST} | cut -d- -f3)
>> >
>> You can do this without resort to an external process:
>> IFS=-
>> read _ _ spec _ &
Donnie Berkholz wrote:
> spec=$(echo ${CHOST} | cut -d- -f3)
>
You can do this without resort to an external process:
IFS=-
read _ _ spec _ <<< "$CHOST"
unset IFS
- or you can do:
IFS=-
arr=($CHOST)
unset IFS
spec=${arr[2]}
- which is useful if you don't know how many elements there are.
(IFS wou
Denis Dupeyron wrote:
> Mike is also an
> amateur cyclist who logs a bit over 4000 miles a year, with a racing
> career that has slowly given away to age.
Aww ;)
> Yes people, Mike is older
> than Uncle Seemant, and even older than me. So kids, please, don't go
> and disturb him while he's having
Roy Marples wrote:
> On Tue, 2007-10-02 at 17:02 -0600, Joe Peterson wrote:
>> Mike Frysinger wrote:
>> > wrong. bash and GNU prevail because they provide useful extensions.
>> > it may be worthwhile to force `find` in the portage environment to be
>> > GNU find so we can stop wasting time tryin
Roy Marples wrote:
> On Tue, 2007-10-02 at 19:37 +0100, Steve Long wrote:
>> Roy Marples wrote:
>> > With [[ ]] you don't need to quote, which encourages people not to
>> > bother learning when and when not to quote.
>> >
>> Ugh, that is so untrue
Roy Marples wrote:
> With [[ ]] you don't need to quote, which encourages people not to
> bother learning when and when not to quote.
>
Ugh, that is so untrue imo. In #bash most people don't know [[ and use [
without quoting, as well as leaving out quotes elsewhere. Which is why we
beat them over t
Mike Frysinger wrote:
> On Tuesday 02 October 2007, Roy Marples wrote:
>> I like consistency too, and I'll be pushing for using sh instead of
>> forcing bash.
>
> pushing a new standard by slowly converting the tree is not the way to go.
>
>> My motivation? Simple. I don't believe that the porta
Roy Marples wrote:
> On Tue, 2007-10-02 at 08:35 +0200, Natanael Copa wrote:
>> After a quick look I wonder how/if it deals with:
>>
>> 1.01 < 1.1
>
> It treats them the same way
>
> [EMAIL PROTECTED] ~ $ bash -c '. /usr/portage/eclass/versionator.eclass;
> version_compare 1.01 1.1; echo $?'
>
Jorge Manuel B. S. Vicetto wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chris Gianelloni wrote:
>> On Mon, 2007-10-01 at 21:54 +, Jorge Manuel B. S. Vicetto wrote:
>>> 1. Due to the tardiness in the election process, there was no council
>>> meeting in September. Will this cou
Mike Frysinger wrote:
> On Monday 01 October 2007, Steve Long wrote:
>> A place to start might be a list of all known variables from say the
>> devmanual, along with whether they're allowed to be used as
>> multi-parameters in `for' or function/cmd calls. So it'
Mike Frysinger wrote:
> On Sunday 30 September 2007, Zac Medico wrote:
>> Donnie Berkholz wrote:
>> > On 04:52 Sat 29 Sep , Mike Frysinger wrote:
>> >> does this work with multilines ?
>> >> if [[ -e ${S}/asdfasdfasdf && \
>> >>-f ${WORKDIR}/moo ]]
>> >> then
>> >>
>> >> this is a crappy e
Donnie Berkholz wrote:
> On 13:15 Wed 26 Sep , Mart Raudsepp (leio) wrote:
>> mv "${D}"/usr/$(get_libdir)/python${PYVER}/site-packages/pygtk.py \
>> "${D}"/usr/$(get_libdir)/python${PYVER}/site-packages/pygtk.py-2.0
>> mv "${D}"/usr/$(get_libdir)/python${PYVER}/site-packages/pygtk.pth \
>> "${
Donnie Berkholz wrote:
> On 17:53 Wed 26 Sep , Doug Goldstein wrote:
>> Mike Frysinger wrote:
>> > Donnie Berkholz wrote:
>> > also, ebuilds do change over time, so what line # may be correct one
>> > day may not be relevant the next ...
>> >
>>
>> Which could bring up a point of would it b
Donnie Berkholz wrote:
> On 05:14 Wed 26 Sep , Mike Frysinger wrote:
>> if it's all common shell, it's pretty hard to hide ... you could try some
>> tricks like rewriting USE to __USE__ so internal code (like the `use`
>> function) still work, but in the end, does that really help ?
>
> I thi
Steve Long wrote:
> Bo Ørsted Andresen wrote:
>
>> On Monday 24 September 2007 21:56:49 Donnie Berkholz wrote:
>>> > if [[ "$(gcc-major-version)" -gt "3" ]] || \
>>> > ( [[ "$(gcc-major-version)" -eq "3" ]] && [[
Robert Buchholz wrote:
> On Tuesday, 25. September 2007, Donnie Berkholz wrote:
>> On 20:04 Mon 24 Sep , Doug Goldstein (cardoe) wrote:
>> > if ! use usb; then
>> > sed -i util/Makefile \
>> > -e '/ttusb_dec_reset/d' \
>> > -e '/dib3000-watch/d'
>> > fi
>> >
>> > # do not compile test-progs
>>
Bo Ørsted Andresen wrote:
> On Monday 24 September 2007 21:56:49 Donnie Berkholz wrote:
>> > if [[ "$(gcc-major-version)" -gt "3" ]] || \
>> > ( [[ "$(gcc-major-version)" -eq "3" ]] && [[ "$(gcc-minor-version)" -gt
>> > "3" ]] )
>>
>> Code block { } might be good here instead of a subshell, or per
101 - 200 of 518 matches
Mail list logo
