On Thu, 13 Jul 2006 02:41:26 +0200 "Diego 'Flameeyes' Pettenò"
<[EMAIL PROTECTED]> wrote:
| > if these use doins/man/doc then the should probably check them
| > before installing:
| > [ -f ${doc} ] && dodoc ${doc}
|
| dodoc of 30 files of which some might not exists take less runtime
| than 30 chec
On Thursday 13 July 2006 02:26, Daniel Black wrote:
> 4. FEATURES="noauto" ebuild {package}.ebuild install
FEATURES=noauto has broken at least two times in different ways with portage
2.1 pre-releases.
Same as broke FEATURES=digest and FEATURES=autoaddcvs or whatever that was.
I won't rely on th
On Thursday 13 July 2006 07:36, Steve Dibb wrote:
> Henrik Brix Andersen wrote:
> > On Wed, Jul 12, 2006 at 11:11:01PM +0200, Jakub Moc wrote:
> >> Uh... Sorry but it's pretty hard to imagine something more annoying than
> >> an ebuild that dies after a couple of hours compile just because
> >> ups
On Monday 10 July 2006 14:38, Joshua Jackson wrote:
> So who's planning on going? Basically I'd like to know who's planning
> on going. I'm still undecided about it honestly, and if I go it'd only
> be for a few days. Its also probably a good way to find a roomate to
> make the cost of rooms a bit
On Tuesday 11 July 2006 09:37, Stuart Herbert wrote:
> On 7/11/06, Gustavo Felisberto <[EMAIL PROTECTED]> wrote:
> > I'm removing net-misc/ssh from the tree as Tectia no longer provides a
> > "free" version of they're ssh client and server. The last update to this
> > package was one year and half
On Wed, 12 Jul 2006 14:46:32 -0700 Donnie Berkholz
<[EMAIL PROTECTED]> wrote:
| It couldn't, but this change isn't being made with a bump. We haven't
| been assured those doing the change right now are going to test every
| package using doman, dodoc, etc.. Packages will probably start failing
| le
On Wednesday 12 July 2006 14:36, Steve Dibb wrote:
> Well, it could happen while testing an ebuild. :) I'd be pretty ticked
> if I were testing Qt and I didn't realize they did change the doc files
> around before doing a test run.
>
> Besides that though, imho, a simple function with a boolean re
Henrik Brix Andersen wrote:
> On Wed, Jul 12, 2006 at 11:11:01PM +0200, Jakub Moc wrote:
>> Uh... Sorry but it's pretty hard to imagine something more annoying than
>> an ebuild that dies after a couple of hours compile just because
>> upstream decided to rename Changelog.txt to ChangeLog.txt and n
Henrik Brix Andersen wrote:
On Wed, Jul 12, 2006 at 11:11:01PM +0200, Jakub Moc wrote:
Uh... Sorry but it's pretty hard to imagine something more annoying than
an ebuild that dies after a couple of hours compile just because
upstream decided to rename Changelog.txt to ChangeLog.txt and noone
Stefan Schweizer wrote:
> > Though if someone is willing to maintain a vanilla xpdf ebuild I'd have no
> > complaints. Genstef?
> >
> I have no complaints either. If there is exg doing the security bumps and
> taking care of the upstream version I am supporting it.
I would have no problem in doin
On Wednesday 12 July 2006 23:21, Henrik Brix Andersen wrote:
> How could that slip through the initial testing of the ebuild
> performed by the developer doing the version bump?
I think that is the point, during testing. If I'm testing the version bump of
something that takes 2 hours to build, I'l
Jakub Moc wrote: [Wed Jul 12 2006, 05:11:01PM EDT]
> Uh... Sorry but it's pretty hard to imagine something more annoying
> than an ebuild that dies after a couple of hours compile just
> because upstream decided to rename Changelog.txt to ChangeLog.txt
> and noone noticed during version bump, or
On Wed, 12 Jul 2006 23:11:01 +0200 Jakub Moc <[EMAIL PROTECTED]> wrote:
| Stefan Schweizer wrote:
| > Jason Stubbs called for consistency .. i.e making doman and dodoc
| > also die when nothing the file does not exist. A simple workaround
| > in case an ebuild is broken: [ -f xxx ] && dodoc xxx
|
On Wed, Jul 12, 2006 at 11:11:01PM +0200, Jakub Moc wrote:
> Uh... Sorry but it's pretty hard to imagine something more annoying than
> an ebuild that dies after a couple of hours compile just because
> upstream decided to rename Changelog.txt to ChangeLog.txt and noone
> noticed during version bu
Stefan Schweizer wrote:
> Jason Stubbs called for consistency .. i.e making doman and dodoc also die
> when nothing the file does not exist. A simple workaround in case an ebuild
> is broken: [ -f xxx ] && dodoc xxx
Uh... Sorry but it's pretty hard to imagine something more annoying than
an ebuild
Aron Griffis wrote:
> Stefan Schweizer wrote: [Wed Jul 12 2006, 01:37:44PM EDT]
>> This came up in Bug 138792 [dobin etc. should automatically die on
>> failure]
>
> Since do* would become functions in this case, you'll have to fix the
> few ebuilds that use them on the RHS of xargs.
>
> gre
Am Mittwoch, 12. Juli 2006 15:36 schrieb Jakub Moc:
> Danny van Dyk wrote:
>
> Wrt the pcmcia thing, well not really ebuilds' fault, see
> http://bugs.gentoo.org/show_bug.cgi?id=122868
Yeah, genstef is working on it.
> There are already bugs filed for some of the rest, please go fix them
> ;)
>
>
On Tuesday 13 June 2006 01:00, Stephen Bennett wrote:
> My current idea is to draw up a formal specification of what ebuilds
> are allowed to do, and what to assume about the environment in which
> they run, as well as defining the formats of everything under
> profiles/, metadata.xml files, and ot
Am Mittwoch, 12. Juli 2006 17:00 schrieb Aron Griffis:
> Danny van Dyk wrote: [Wed Jul 12 2006, 09:16:30AM EDT]
>
> > There are 505 ebuilds which are missing use flags in IUSE that they
> > use in other places.
Much of those 505 violations are a missing pcmcia flag, which i stopped
to fix once i
[EMAIL PROTECTED] wrote:
> I really would like to see back the upstream version, what do you think?
I don't think anybody would mind you putting them into the tree again.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
Stefan Schweizer wrote: [Wed Jul 12 2006, 01:37:44PM EDT]
> This came up in Bug 138792 [dobin etc. should automatically die on failure]
Since do* would become functions in this case, you'll have to fix the
few ebuilds that use them on the RHS of xargs.
grep -r --include \*.ebuild -E 'xargs d
Sune Kloppenborg Jeppesen wrote:
> On Wednesday 12 July 2006 16:43, [EMAIL PROTECTED] wrote:
> > Guys,
> >
> > The xpdf version we have currently in the tree is a modified one that
> > links to poppler, provided in IRC to genstef by an ubuntu developer (no,
> > ubuntu does not use it); now, I can u
Hi,
This came up in Bug 138792 [dobin etc. should automatically die on failure]
It needs more discussion on the mailing lists.
Some excerpts from the bug: The proposal from Paul Bredbury:
"Hi, I propose that the following ebuild commands themselves *die* on
failure, because the vast majority of th
Sune Kloppenborg Jeppesen wrote:
> On Wednesday 12 July 2006 16:43, [EMAIL PROTECTED] wrote:
>> I really would like to see back the upstream version, what do you think?
> The reason for this was security I believe. xpdf code is embedded in lots
> of other packages (see http://glsa.gentoo.org for so
On Wed, 12 Jul 2006 15:23:06 +0200 Matthias Schwarzott
<[EMAIL PROTECTED]> wrote:
| IUSE="" # don't put pcmcia here, rather in the ebuilds that actually
| support pcmcia
That's not legit. An eclass should list all USE flags that it itself
uses. Similarly, an ebuild should list all USE flags that i
On Wednesday 12 July 2006 16:43, [EMAIL PROTECTED] wrote:
> Guys,
>
> The xpdf version we have currently in the tree is a modified one that
> links to poppler, provided in IRC to genstef by an ubuntu developer (no,
> ubuntu does not use it); now, I can understand that having a single
> point of fai
Danny van Dyk wrote: [Wed Jul 12 2006, 09:16:30AM EDT]
> There are 505 ebuilds which are missing use flags in IUSE that they use
> in other places.
I once wrote a script (attached) to update IUSE automatically. To use
it, simply:
$ cd games-emulation/xmess
$ fixiuse
It reports what it changed
Guys,
The xpdf version we have currently in the tree is a modified one that
links to poppler, provided in IRC to genstef by an ubuntu developer (no,
ubuntu does not use it); now, I can understand that having a single
point of failure is desiderable, but I completely disagree when doing
this implie
Am Mittwoch, 12. Juli 2006 15:23 schrieb Matthias Schwarzott:
> On Wednesday 12 July 2006 15:16, Danny van Dyk wrote:
> > Hi all,
> While reading your list I have seen pcmcia often. e.g. on my ebuild
> v4l-dvb-hg not supporting pcmcia as conditional. A bit digging showed
> that linux-mod.eclass co
Danny van Dyk wrote:
> Hi all,
>
> thanks to djm's efforts i was just able to scan the whole tree using
> qualudis. For a start, i'll attach a list of QA violations on missing
> entries in IUSE. As this is a minor change to the ebuilds, I'll go on
> and fix all the listed ebuilds myself.
>
> T
On Wednesday 12 July 2006 15:16, Danny van Dyk wrote:
> Hi all,
>
> thanks to djm's efforts i was just able to scan the whole tree using
> qualudis. For a start, i'll attach a list of QA violations on missing
> entries in IUSE. As this is a minor change to the ebuilds, I'll go on
> and fix all the
Hi all.
Just a quick reminder that you can only rely on static things in most
top-level variables in ebuilds. See
http://devmanual.gentoo.org/general-concepts/portage-cache/index.html
for details.
For a "real world" example on how to break the cache see
http://sources.gentoo.org/viewcvs.py/gentoo
32 matches
Mail list logo