-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lisa Seelye wrote:
| We have quantum chemistry and molecular dynamics packages?
Sure we do. I've been maintaining most of them, and it's been great to
see more packages showing up recently (and more help, too).
Donnie
-BEGIN PGP SIGNATURE-
V
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego 'Flameeyes' Pettenò wrote:
| What I want to hear is if anyone has good reasons to not allowing
| choosing the tar command between the two compatible alternatives (both
| works fine with portage). If nobody has reasons, I'll be back in a
| coup
Jakub Moc wrote:
would someone more competent explain to me, why
- this feature even exists
It makes sense to enable support for packages you have installed. This
should be the default behavior, and it should require manually disabling.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lisa Seelye wrote:
| With bug 80219 a user posted a patch for OpenSLP support with Distcc
| based off of the 2.18.3-r7 ebuild. I can't seem to make it work so I'm
| going to ask the dev mail list to see if anyone else can test and make
| it work. Pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lisa Seelye wrote:
| On Sun, 2005-11-20 at 11:38 -0800, Donnie Berkholz wrote:
|>Out of curiosity, why isn't this patch just being sent upstream for
|>incorporation there?
|
|
| It is, but there hasn't been much work on Distcc this y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ned Ludd wrote:
| On Sun, 2005-11-20 at 14:45 -0800, Donnie Berkholz wrote:
|>Our policy for X is that if upstream won't accept it, we won't either.
|>Perhaps you'd be interested in adopting that and convincing the repor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Because portage treats the default virtual differently than I was
previously led to believe, everybody who's ported a package to modular X
so far will need to make a small change.
It's really easy, but it might take a bit of time to go through your
p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego 'Flameeyes' Pettenò wrote:
| On Monday 21 November 2005 21:50, Donnie Berkholz wrote:
|
|>Here's the change:
|>"virtual/x11" -> "<=x11-base/xorg-x11-6.99"
|
| Is this the last change? :)
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Lohrke wrote:
| On Monday 21 November 2005 21:50, Donnie Berkholz wrote:
|
|>Here's the change:
|> "virtual/x11" -> "<=x11-base/xorg-x11-6.99"
|
|
| virtual/x11 isn't xorg for all profiles.
Perhaps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua Baergen wrote:
| If the list keeps growing maybe we should consider a GLEP 37-style
| solution, like was suggested by Jason. It would allow us to make any
| further changes that are required (agreed, hopefully none) without
| having to change a
Doug Goldstein wrote:
I thought GLEP 37 was a way out kind of thing. Like several months if
not a year before it can be done.
I figured about the same, but
https://bugs.gentoo.org/show_bug.cgi?id=112896#c16 begs to differ.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
Jakub Moc wrote:
*Now* I hope I've finally been sarcastic enough to justify the incredibly
pissed-off tone you've shown in your previous reply. I've not exactly seen any
flames or name calling here, and I'm not the one to blame for the fact
that you're feeling overloaded. Jump back in when you ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luis F. Araujo wrote:
| So, i wrote a script to try to get a list of those orphaned entries,
| and it looks like there are more than 400 packages/ebuilds which are still
| listed in p.m but that don't exist in the tree anymore.
| (A bunch of them from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Curtis Napier wrote:
| The contents of the uppermost menu are to sites that are outside the
| www.gentoo.org website. They will stay in this location. They are green
| to contrast with the purple background to ensure that colorblind and
| other visual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
| These packages do not need shadow (though the system might, but that's
| outside my scope) once they are installed, only to install. However, it
| is not needed to build. What *DEPEND is correct?
It fits into RDEPEND (oddl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
| That is what I thought. I was just wondering if there were some other
| *DEPEND that I wasn't aware of that fit the bill of "needed for
| installing from a package but not needed afterwards". It doesn't
| *really* matter si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Brix Andersen wrote:
| I've read the initial post a couple of times now, and I still don't
| get it.
|
| Could somebody please clarify how this differs from DEPEND?
Because DEPEND is only needed for the actual build (src_* functions).
With bin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego 'Flameeyes' Pettenò wrote:
| Possible solutions I thought of:
|
| 1) have every herd controlled by a project
This should be the goal already, and all herds should be looking to
either join or create a project, in conjunction with other herds.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lina Pezzella wrote:
| I would want to know exactly how many keywords would be dropped with
| this solution. I would hate to see something that is working perfectly
| fine having support dropped due to syntax troubles in an ebuild...
Portage's lack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
With 7.0rc3 that's been entering the tree last weekend, there was an ABI
change in libdrm and subsequent bump from .so.1 to .so.2.
This means you'll need to run revdep-rebuild after upgrading, otherwise
you'll get problems from 3D just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Forman wrote:
| On Tue, 2005-12-06 at 00:48 -0500, Jeffrey Forman wrote:
|>This is just an 7-8 hour warning for the coming downtime of
|>bugs.gentoo.org for upgrade. I plan to upgrade bugzilla the morning
|>(EDT) of December 7th. I plan on alo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| As far as progress on this issue, we're looking into adopting glep 37
| and creating a virtual/x11 ebuild to address this.
I've just committed virtual/x11 to the tree. See
https://bugs.gentoo.org/show_bug.cgi?id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
| On Wednesday 07 December 2005 17:03, Donnie Berkholz wrote:
|
|>Donnie Berkholz wrote:
|>| As far as progress on this issue, we're looking into adopting glep 37
|>| and creating a virtual/x11 ebuild to address t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm planning on porting every installed app on my system to modular X,
starting in the next couple of days. This means I will be committing to
many of your applications, libraries, etc.
If you don't trust my ability to do this or otherwise don't want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| I'm planning on porting every installed app on my system to modular X,
| starting in the next couple of days. This means I will be committing to
| many of your applications, libraries, etc.
|
| If you don't trust
Ciaran McCreesh wrote:
So is there now a safe, correct way of specifying modular X
dependencies that will actually work?
It will work when I pull the virtual/x11 from base/virtuals this
weekend. Until then, it will wrongly think xorg-x11-7 ebuilds provide
the virtual.
See my recent post on
Donnie Berkholz wrote:
For your benefit, here's my world file. You can determine whether your
app's in the list by replacing yours with it, then running 'emerge -ep
world'.
It was pointed out that I worded this poorly. Rather than replacing, you
should back up your ow
Donnie Berkholz wrote:
I plan to remove the virtual/x11 definition from base/virtuals in a
couple of days, because this should provide a full (and non-broken)
replacement.
Done.
I will probably do similar for the other x11 virtuals (particularly xft)
soon, assuming this doesn't brea
Joshua Baergen wrote:
In an attempt to patch all driver packages automatically, I've modified
x-modular.eclass to do something along the lines of what elibtoolize
does for its patching. However, this would require the storage of a
patch for x-modular.eclass, which I would intend to place in a
AREAS WE NEED HELP WITH:
1) Porting applications to modular X
2) Fixing descriptions for the vast majority of modular packages.
OK, it seems like we've now got issues resolved related to the new
virtual/x11 package. Despite all the eyes that looked at it and all the
publicity on lists and else
Martin Schlemmer wrote:
Will need to do something about the default glu/opengl/xft virtuals as
well ... (you probably did not forget this, just double checking ...)
Yep.
From an email I sent in the past 24 hours:
Donnie Berkholz wrote:
> Done.
>
> I will probably do similar for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
| so the video herd policy is to remove packages until you're left with
| a small enough subset of packages you can handle ?
Quite a contrast with the x11 herd policy: to add packages until there's
10x more than you can reasonab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Skeggs wrote:
| Am Freitag, den 09.12.2005, 23:12 + schrieb Donnie Berkholz:
|
|>2) Users with no X installed will pull in the virtual/x11 package
|>because there is no longer a default virtual.
|
| A user in #gentoo-amd64 ran into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've just updated the two dependency-finding scripts for libraries and
includes. The library one should get significantly faster because of
some optimizations on grepping the log; it also works better (less false
positives) in most cases. The include
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| I'm planning on porting every installed app on my system to modular X,
| starting in the next couple of days. This means I will be committing to
| many of your applications, libraries, etc.
I've finished roughly
George Prowse wrote:
yes but if you extracted a stage on to an already built system you would
not only have the the mess there that you wanted to get rid of but also
all your config files would revert back to older versions and you'd lose
any changes made.
...
because i'd rather not use depc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| I'm planning on porting every installed app on my system to modular X,
| starting in the next couple of days. This means I will be committing to
| many of your applications, libraries, etc.
I am pleased to announce I&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Lauer wrote:
| On Thu, 2005-12-15 at 07:43 -0700, Duncan wrote:
|>This really belongs on user, or perhaps on the appropriate purposed list,
|>desktop or hardened or whatever, not on devel. That said, some
|>comments... (I can't resist. )
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Loeser wrote:
| Mark Loeser <[EMAIL PROTECTED]> said:
|
|>So, everyone that has a binary package in the tree, I would appreciate
it if
|>you could put the sys-libs/libstdc++-v3 depend into your package if
|>necessary.
|
|
| Well, you can tell I d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I know some of you have done research on how gentoo-x86 converts over to
other systems besides CVS such as SVN, arch, etc. But I can't find the
info anywhere in my archives.
Could whoever's got it, post it?
I'm particularly interested in he
Jakub Moc wrote:
the virtual/ thingy broke the deptree again with virtual/libstdc++ (see Bug
116253), essentially the same issue like with virtual/x11. These virtuals
need to go straight stable if any of their RDEPEND atoms is stable for a
particular arch.
Shouldn't it be the reverse? Rather, t
Donnie Berkholz wrote:
I know some of you have done research on how gentoo-x86 converts over to
other systems besides CVS such as SVN, arch, etc. But I can't find the
info anywhere in my archives.
Could whoever's got it, post it?
I'm particularly interested in hearing about CVS,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd appreciate some ideas better than what I've come up with so far to
deal with the very strange X.Org release naming.
When modular tarballs are part of a full X.Org release (7.0, 7.1, etc),
then they are named PN-PV-XORG_RELEASE.tar.(gz|bz2) and S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ferris McCormick wrote:
| On Wed, 2005-12-21 at 21:34 -0800, Donnie Berkholz wrote:
| What does this mean for the future? All modular X ebuilds that are part
| of a full release will require XORG_PV to be set. All modular X ebuilds
| that aren't
)
iD8DBQFDqt2XXVaO67S1rtsRAlzuAJwJooVqex46LHMYcYTDx40kUn6/WgCgrlgr
KUC845ELqhXHZ5ZNs6PkUbQ=
=Z5KJ
-END PGP SIGNATURE-
#!/bin/bash
# This is a script to read portage log items from einfo, ewarn etc, new in the
# portage-2.1 series.
#
# Author: Donnie Berkholz <[EMAIL PROTECTED]>
# Set PORTAGE_TMPDIR
PORTAGE_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| I'd appreciate some ideas better than what I've come up with so far to
| deal with the very strange X.Org release naming.
|
| When modular tarballs are part of a full X.Org release (7.0, 7.1, etc),
| then they are n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul de Vrieze wrote:
| On Thursday 15 December 2005 16:50, Donnie Berkholz wrote:
|>gentoo-performance Discussions about improving the performance of
Gentoo
|>
|>Although it was a bit quiet last time I was subscribed to it.
|
|
| I
Greg KH wrote:
For those of us who want to try modular now, where's the pointer to how
to do this (I can't seem to find it in the archives, sorry...)
I've been meaning to get it into guidexml and make it a real project doc
for a while now (and the accompanying porting guide), but haven't had
Joshua Baergen wrote:
As many of you no doubt have noticed, spyderous and I finished bumping
the modular packages to the newly released 7.0, which includes many
changes and bug fixes since 6.8.2. Over the next few weeks we'll be
finalizing licenses and other necessities. To whoever has been u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| See the part that I said "make sense to take out". What you described is
| a perfect example of something that needs to stay. All I'm getting at is
| that minor things that the package maintainer thinks isn't important to
| ke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| Mike Frysinger wrote:
|
|
|>If you have something you'd wish for us to chat about, maybe even
|>vote on, let us know ! Simply reply to this e-mail for the whole
|>Gentoo dev list to see.
|
|
| Gentoo has been missing some kin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Stelling wrote:
| My point is, either you have to generalize each project's goal to a real
| triviality or you have to define a goal which doesn't match some
| project's goals. Conclusion: Let it be.
Not necessarily. I just wrote on my blog [1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
| On Tue, 03 Jan 2006 09:28:24 -0800 Donnie Berkholz
| <[EMAIL PROTECTED]> wrote:
| | Here's one example of a global goal: Reduce the learning curve of
| | Gentoo and increase its usability.
|
| That goal i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
| As a prime example, I strongly believe that making Gentoo "as easy as
| possible" can only come about by reducing its usability. If there is a
| large number of choices, no matter how well documented, it isn't easy
| for a b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Stelling wrote:
| Donnie Berkholz wrote:
|> - - Releng would work to ensure that installing Gentoo is as easy as
|> possible.
|
|
| This is very vague too. Easy for who? Easy for a user who is too lazy to
| read docs and doesn'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| All of those of course are true. I guess I'm thinking more in the large
| picture of things. Retiring non-active devs isn't something I'd exactly
| call 'ground breaking' :-). I know there are things being worked on now
| that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg KH wrote:
| On Mon, Jan 02, 2006 at 01:56:03PM +0530, Shyam Mani wrote:
|
|>[2] http://www.gentoo.org/doc/en/modular-x-howto.xml
|
|
| You mean:
| http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml
| right?
Yeah we decided to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Lauer wrote:
| Hi all,
|
| I recently ran into an interesting problem:
|
| One app I have seems to trigger a bug in Python 2.4, so I want to use it
| with Python 2.3
| But, as it imports a few python modules I can't use it - the modules
| only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kurt Lieber wrote:
| On Thu, Jan 05, 2006 at 12:39:05AM -0500 or thereabouts, Alec Warner
wrote:
|>The Gentoo Installer is an interesting project, not only for the
|>graphical frontend, but for the Distro-sponsored Network installer that
|>is being wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Gianelloni wrote:
| Funny enough... I was working on this and forgot to send it out.
|
| I was planning on posting it also on the Release Engineering page, but
| need to turn it into GuideXML first.
Might want to run it through spellcheck first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| As seen from the discussion earlier this week, I don't think Gentoo has
| the proper open-mindness to create a proper enterprise distro. There are
| too many things that would get in the way of Gentoo proper to make it
| work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Portnoy wrote:
| On Fri, Jan 06, 2006 at 01:37:45AM -0700, Duncan wrote:
|
|>What word to use in place of "distribution", when one wants to include the
|>BSDs and other "non-distributions" as well, other than
|>Linux/BSD[/*ix]][/OSX], or simply *i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefaan wrote:
| I don't use pmount myself, but my guess is that /media is just a
| directory that contains mountpoints, and which remains at all time
| writeable for root. /afs is not writeable when mounted, just like
| /dev/cdrom etc...
That's actu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stuart Herbert wrote:
| I agree that some cleaning is needed (and some of my packages are
| desperate for it!), but I'm totally opposed to this idea. I think the
| idea of shutting up shop for three months (presumably with a "closed
| for refurbishme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Muraco wrote:
| Another thing that I don't like, is the feel of this method does seem
| "offical" enough.. mostly because portage is not 'stable'-aware, Its
| just using a stripped down tree.
What do you want then? If an entire standalone tree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Vermeulen wrote:
| We have already received many bugs for documentation in /proj/* which is
| not GDPs. I had no issue with this as I hoped this would be a transient
| state where the documentation is eventually handed over to the GDP so that
| b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| What if instead of having proj/en we did herd/en on www? Of course, that
| doesn't help the whole "GuideXML is hard" bit. I like the idea of using
| RST, but it doesn't seem very scalable at this time. Maybe, instead of
| that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| Donnie Berkholz wrote:
|
|>Lance Albertson wrote:
|>| What if instead of having proj/en we did herd/en on www? Of course, that
|>| doesn't help the whole "GuideXML is hard" bit. I like the idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| Chris Gianelloni wrote:
|>I think that would be a wonderful idea. What would we do about herds
|>that are a project? Simply throw in a redirect under the herd name to
|>the project name?
|>
|
|
| Unless they already reside i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lance Albertson wrote:
| But herd != project. They are two distinct things. There are a couple of
| cases where they both are the same, but others where it isn't. For
| example, what project would netmon fit under? They aren't actively
| trying to cre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
| I don't want to get into the habit of inconsistency and finding herds in
| two different locations.
To clarify, add an "either" onto the end of that.
| Thanks,
| Donnie
-BEGIN PGP SIGNATURE-
Versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg KH wrote:
| Well, it's not a Gentoo specific plea, but a Linux kernel plea. I've
| created a new kernel tree, git-sources, that tracks the upstream
| development kernel tree every day (not the raw git tree, but the nightly
| snapshots of it.)
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg KH wrote:
| On Tue, Jan 10, 2006 at 10:27:46AM -0800, Donnie Berkholz wrote:
|>Where should people file bugs on this?
|
|
| To quote the einfo text that is shown when you install this kernel:
| This kernel is not supported by Gentoo due
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stuart Herbert wrote:
| Don't you think that maybe you're trying to bash square pegs into
| round holes just for the sake of some sort of order that perhaps
| doesn't actually benefit anyone at all?
|
| Where did the requirement that a herd has to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sanchan wrote:
| Alexandre Buisse wrote:
|
|>I don't know TinyOS, but I assume it is a "toy OS", like minix and
many others.
|>What about a dev-toyos category? It could be great to have some other
|>toy OS, including the one I have been working on (fu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexandre Buisse wrote:
| Hi,
|
| for all of you who have been using latex on gentoo, here are some news
| on what is currently happening.
|
| First of all, we have a new tetex (tetex-3.0_p1). It should have hit the
| mirrors this morning. This is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Frysinger wrote:
| yes, but fbsd is a self hosting env, tinyos is not
|
| i wish there was a way we could convey the embedded aspect (embed-tos
?), but
| dev-tos works for me
Why stuck on "tos" -- Just spend the other 3 letters and make it tinyo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Proschofsky wrote:
| Hi everyone,
|
| I've added a new local use flag called "binfilter" to
| app-office/openoffice. This enables building support for legacy
| StarOffice 5.x file formats. My advice: Only build with this, if you
| really need
I hacked together a script this afternoon to find any packages that are
not yet ported to modular X. It will only work on systems _with modular
X installed_. This is because it works by using emerge to check for
blockers, then resolving those blockers down to a single package.
Try it out and let
Donnie Berkholz wrote:
I hacked together a script this afternoon to find any packages that are
not yet ported to modular X. It will only work on systems _with modular
X installed_. This is because it works by using emerge to check for
blockers, then resolving those blockers down to a single
Donnie Berkholz wrote:
Donnie Berkholz wrote:
I hacked together a script this afternoon to find any packages that are
not yet ported to modular X. It will only work on systems _with modular
X installed_. This is because it works by using emerge to check for
blockers, then resolving those
Donnie Berkholz wrote:
And here's a list, with herds and maintainers, of a loop across each
category in PORTDIR. This should be a fairly comprehensive list of every
app not yet ported.
Today's update, synced as of about an hour ago, along with the script to
generate everything if y
Sebastian Bergmann wrote:
Donnie Berkholz schrieb:
dev-php/PECL-imagick php none
This package only has
DEPEND="${DEPEND} >=media-gfx/graphicsmagick-1.0.0"
listed as its dependencies.
Ah, yes. It will also catch whether anything in the dependency tree of
any app is bro
Donnie Berkholz wrote:
I hacked together a script this afternoon to find any packages that are
not yet ported to modular X. It will only work on systems _with modular
X installed_. This is because it works by using emerge to check for
blockers, then resolving those blockers down to a single
Donnie Berkholz wrote:
My current script seems to miss some things. The reason this happens is
that the group of applications they're emerged in also contains some app
that breaks the emerge, perhaps because it's in package.mask or isn't
keyworded at least ~x86. Broken emerge
Donnie Berkholz wrote:
OK, I've got this fixed. Suddenly there are 1037 unported apps instead
of 500! How exciting.
Today's update.. down to 1012 packages.
Donnie
app-accessibility/brltty accessibility dmwaters
app-accessibility/dasher gnome-accessibility none
app-accessibility
Lares Moreau wrote:
Could you post updates once a week(or two), similar to what [EMAIL PROTECTED]
does with the aging ebuilds. I don't feel a play-by-play is necessary.
I will be posting daily updates until it goes into ~arch, planned for
Jan. 25.
Thanks,
Donnie
signature.asc
Description: O
Dan Meltzer wrote:
Would you considder putting these daily updates on your devspace
instead of sending a huge email daily?
Nope. That puts the effort on these developers who haven't ported apps
to actually go to my webspace and search around.
On re-reading what you said, I could post a link to
Alec Warner wrote:
Did you find another way to do those deps then? We haven't released
2.0.54 with that fixed yet...
The drivers will continue to require manual emerging in ~arch until a
fixed portage comes out, and the migration guide continues to document
and support that method.
Thanks,
Do
Mike Frysinger wrote:
- we will set sane debug defaults in the base profile:
* DEBUG_CFLAGS=DEBUG_CXXFLAGS="-O -g"
On gcc-4, even -O can make it really hard to track stuff. Might want -O0
instead. 4.1 gets even crazier.
Thanks,
Donnie
signature.asc
Description: OpenPGP digital signature
Donnie Berkholz wrote:
Today's update.. down to 1012 packages.
Yesterday was pretty weak, only 9 packages got ported. We're at 1003 now.
Latest list:
http://dev.gentoo.org/~spyderous/broken_modular/broken_modular_maintainers.txt.20060120
Documentation:
http://www.gentoo.org/proj/en
You definitely made up for Thursday's performance yesterday by dropping
the number of unported packages from 1003 to 917.
I've posted a graph of our progress [1]. Keep up the good work of the
past day, and the tree will be in great shape in time for modular X to
enter ~arch.
Latest list:
http://d
Marius Mauch wrote:
> On Sun, 22 Jan 2006 14:45:34 -0500
> Mike Frysinger <[EMAIL PROTECTED]> wrote:
>
>> On Saturday 21 January 2006 23:12, Marius Mauch wrote:
>>> Mike Frysinger wrote:
On Sunday 15 January 2006 01:11, Mike Frysinger wrote:
- we add an emerge flag (say '--debug-bui
Yesterday's drop: 17 to 871. Not as impressive as Saturday, but not bad.
Progress graph:
http://dev.gentoo.org/~spyderous/broken_modular/broken_modular_progress.png
Latest list:
http://dev.gentoo.org/~spyderous/broken_modular/broken_modular_maintainers.txt.20060122
Herds and individuals with 10
Donnie Berkholz wrote:
> Yesterday's drop: 17 to 871. Not as impressive as Saturday, but not bad.
Sorry, that's 917. So it dropped by 36.
signature.asc
Description: OpenPGP digital signature
Here's my proposal for dealing with modular X entering ~arch.
Yes, some packages are going to break. But I intend to keep this to a
minimum on packages people care about, as measured by the existence of
an open porting bug.
So here's my plan: Before modular X enters ~arch, I will ensure that all
Ciaran McCreesh wrote:
> On Mon, 23 Jan 2006 23:06:12 -0800 Donnie Berkholz
> <[EMAIL PROTECTED]> wrote:
> | Here's my proposal for dealing with modular X entering ~arch.
>
> What's wrong with the original idea of just making any unported ebuild
> pull in all of
Yesterday's drop: 871 to 867, a whopping 4. We need to do better than
this! We're in the home stretch.
Progress graph:
http://dev.gentoo.org/~spyderous/broken_modular/broken_modular_progress.png
Latest list:
http://dev.gentoo.org/~spyderous/broken_modular/broken_modular_maintainers.txt.20060122
Mike Doty wrote:
> I think before you go forward with something like this you should give a
> suitable period of warning, it's going to create a lot of bug work for
> all of us.
Have you seen my daily emails for the past week and a half? =)
I have the feeling that it will create the most work for
Mark Loeser wrote:
>>> On Mon, 23 Jan 2006 23:06:12 -0800 Donnie Berkholz
>>> <[EMAIL PROTECTED]> wrote:
>>> What's wrong with the original idea of just making any unported ebuild
>>> pull in all of modular X (minus drivers)? Yes, it means that some
1 - 100 of 1428 matches
Mail list logo
