ould take up that much
room. The only reason Tim and myself are listed there is because we are
the ones maintaining it now, and want people to be able to easily find
who they should contact about changes.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - hal
just
haven't gotten around to it yet :)
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0
ause it was all done by hand :)
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpi9PqwvKg3C.
considered "policies" that are outlined in the
document. We will be working on that in the next week or two.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web
trying to get bugs upstream to fix all of these issues.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halc
This package is currently without a maintainer and has open QA issues;
bug #123708. It was marked as testing on every arch without being
tested and could really use someone to clean it up. It will be booted
in 30 days if no one wants to keep it around.
Thanks,
--
Mark Loeser - Gentoo
until the Council has decided
on how we wish to proceed in handling situations like this.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
uld proceed, that we not add anything else to the tree
for the sole reason of supporting another package manager's features.
This includes profiles or any other packages. This will reduce
headaches for all of us, and hopefully cut down on needless arguments
that get us no where.
Thanks,
--
oo's
> patches.)
No, I would get a testcase for the bug and file it upstream. The only
bugs I've marked invalid are for the testing versions of GCC.
But, this is entirely off topic.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gent
ey file a bug about something they did wrong, and this sounds
like it would fill that void.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.or
of them one day replaces Portage,
it will have my complete support, but until then, we should focus on
keeping changes in the tree to a minimum for other package managers.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT or
too.org/proj/en/glep/glep-0048.html
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgp7vJhlF
eed
> to have items expire unless explicitly renewed? Thoughts?
I think this is a good idea. We have some items on there that are years
old, and it would be good to even update the requested date on them so
that people know the requests are still valid.
--
Mark Loeser - Gentoo Developer (cpp gcc
xfsamba was merged into xffm by upstream awhile back, and has been
unmaintained since. It will be removed in 30 days unless someone steps
up to maintain it and fix the bugs it has (bug #127166 for example).
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email
s as herds a lot of the time. It has become a
statement over time that people understand. I'm not sure why we want to
try and change that to something else, even if that was what it was
supposed to mean to begin with.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email
And now in GLEP format for those who like that sort of thing :)
http://www.gentoo.org/proj/en/glep/glep-0048.html
I made the two wording changes so it is more clear what I wanted to
communicate.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n
Duncan <[EMAIL PROTECTED]> said:
> Mark Loeser posted <[EMAIL PROTECTED]>, excerpted
> below, on Mon, 24 Apr 2006 09:11:28 -0400:
>
> >> > * QA will take an active role in cleaning up unmaintained and broken
> >> > packages from the tree
QA team by giving them a
> document that they can direct devs to when there is a problem.
I addressed this in my reply to morfic, basically, it is just the
wording that threw you off :) I mean that it can never be complete, so
don't think it ever is.
--
Mark Loeser - Gentoo Develop
Mark Loeser <[EMAIL PROTECTED]> said:
> Daniel Goller <[EMAIL PROTECTED]> said:
> > Mark Loeser wrote:
> > > Here is the newest revision of my proposal. Not much has changed, but I
> > > added and changed some small things. Constructive feedback is
> &g
Daniel Goller <[EMAIL PROTECTED]> said:
> Mark Loeser wrote:
> > Here is the newest revision of my proposal. Not much has changed, but I
> > added and changed some small things. Constructive feedback is
> > appreciated. I'd like to get this voted on by the
information to avoid past problems.
* QA will take an active role in cleaning up unmaintained and broken
packages from the tree. It is also encouraged of members of the QA team to
assist in mentoring new developers that wish to take over unmaintained
packages/herds.
--
Mark Loeser - G
ning that up. It helps no one
if there isn't anyone to claim responsibility for the package when there
is a problem.
Just my 2 cents,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT
dev-util/ is not depended on by any other applications, the stable
version does not compile, and while upstream has newer releases which most
likely work...there is no Gentoo maintainer (bug #128109). If no one steps
up to maintain it in 30 days, I will be removing it.
--
Mark Loeser
There has been no upstream release in years, and the download URLs no
longer work. It also has some open bugs (bug #127131). If anyone
wishes to step up and maintain this, please do so within the next 30
days, or I am removing it from the tree.
Thanks,
--
Mark Loeser - Gentoo Developer
once they heard about that. The people that walked up to us
and just told us, "You guys rock!" were awesome too :)
Just my two cents, :)
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT hal
hose as well.
This shouldn't happen, but if they believe a group has stepped out of
line... Things should only go to the council when all other methods
fail, and they are the only ones you can appeal to.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email -
hs. It became less a "Code of Conduct" and more of a developer
relations/devrel/whatever policy. Lets keep that out of a document like
this and decide on that through the appropriate channels.
If those last two paragraphs are cut, I'm quite happy with it, even if
it isn't al
"Michael Sterrett -Mr. Bones.-" <[EMAIL PROTECTED]> said:
> You broke deps with that masking. I've commented it in package.mask so
> you can fix that up first.
Yea, I did. Sorry about that. Now x11-misc/paralogger is masked as
well and will be removed at the
Upstream has been dead for years and is unmaintained. Also requires
some reworking to compile with gcc-4; bug #122022. It will be removed
in 4 weeks unless someone steps up to maintain it.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT
Carsten Lohrke <[EMAIL PROTECTED]> said:
> On Thursday 30 March 2006 01:55, Mark Loeser wrote:
> > Not directed specifically at you, but it seems a lot of people are
> > masking stuff and removing it very quickly, and I'd really like to see
> > everyone wait the
ill be removing it in 30 days.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpRW5G91lZr8.
there any reason that the package should be
removed so quickly?
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
much we can do when
there is no one to maintain them.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpoUzwZPe2e2.pgp
Description: PGP signature
k all of the packages if no maintainer can be found
to step up. So, is anyone willing to do so?
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~ha
o their lap when we can make choices for them
which we believe to be sane.
I'd like less errors/dies during the build/deptree phase and more
warnings/information to be presented so the user could look at it and
make changes, or just accept what we have done for them.
--
Mark Loeser
uot; is needed. As he also suggested, we should keep a list of
these in the form of open bugs so that we can get a better solution
somewhere in the long-term.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
gt; decided not to address the points I raised about your original draft:
I never said it was different. I said I added some things based on
feedback I got. As I said in the last thread, I disagree with many of
the things you have come up with. You are free to try and convince me
otherwise.
--
o that.
I don't see where anyone is saying that we shouldn't fix things to
adhere to coding standards. We are just saying it is not a, "OMG you
broke it!" problem. It is about appropriate responses to the problems
we encounter.
--
Mark Loeser - Gentoo Developer (cpp gc
e the weirdness.
I agree. Coding standards, while they may qualify as violations, are
not as severe, but are definitely things we would like to see fixed.
They are there to make readability across ebuilds easier since
everything will be formatted the same way for a developer to see.
--
Mar
olution should be able to be achieved between the QA team and
the maintainer. In situations where we can't figure out how to best
address the situation, opening the discussion up to -dev may help, but
in the end it should come down to an agreement between the maintainer
and the team.
--
M
that we won't always get the perfect solution right away and
that flexibility is required.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http:
Alec Warner <[EMAIL PROTECTED]> said:
> Mark Loeser wrote:
> > Here is my updated version after some feedback from people:
> > * In the case of disagreement on policy among QA members, the majority
> > of established QA members must agree with the action.
>
>
another month, but I'd
like to get all of the debate out of the way now.
Please lets keep the discussion on topic and constructive.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT hal
t expect him to change, not that I expect QA team
members to behave that way.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
cooperate so that Gentoo is the least buggy
> distro of them all when 2006.1 comes out ;-)
Thanks, hopefully enough people have faith in us to do the right thing
so that we can get everything fixed up that we can.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa too
different issue though, and I have talked to Ciaran about it.
What I was saying above is that I am not going to go and get involved
every single time someone has a disagreement. This situation has
obviously grown to be ridiculous and I have had a talk with him about
it, so he knows my feelings on
Grant Goodyear <[EMAIL PROTECTED]> said:
> Mark Loeser wrote:
> > * In case of emergency, or if package maintainers refuse to cooperate,
> > the QA team may take action themselves to fix the problem.
>
> My suspicion is that the more common problem is going to b
should have this right in extreme circumstances.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgp8iRpskxJ5q.pgp
Description: PGP signature
Ciaran McCreesh <[EMAIL PROTECTED]> said:
> On Sun, 26 Feb 2006 17:22:17 -0500 Mark Loeser <[EMAIL PROTECTED]>
> wrote:
> | * The QA team will maintain a list of current "QA Standards". The
> | list is not meant by any means to be a comprehensive document, but
Donnie Berkholz <[EMAIL PROTECTED]> said:
> Mark Loeser wrote:
> > Well, instead of putting the debate into an even larger crowd, this
> > enables the QA team to act in the way it sees best first. If people
> > believe we were wrong, then we give them the option to ta
Stuart Herbert <[EMAIL PROTECTED]> said:
> On Sun, 2006-02-26 at 17:22 -0500, Mark Loeser wrote:
> > * In case of emergency, or if package maintainers refuse to cooperate,
> > the QA team may take action themselves to fix the problem.
>
> I'd like to see this s
we plan to work as much with maintainers as possible, but
sometimes that may prove to be impossible.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gen
first. If people
believe we were wrong, then we give them the option to talk to the
council about one of our changes. Also, we aren't unwilling to hear
alternatives and we hope to work with the maintainer on these problems.
--
Mark Loeser - Gentoo Developer (cpp gcc-p
st breakages will be presented with this request to
devrel.
* The QA team will maintain a list of current "QA Standards". The list
is not meant by any means to be a comprehensive document, but rather a
dynamic document that will be updated as new problems are discovered.
--
Mark Loes
eep it in the tree, step up and fix
the bugs. It will be gone in 4 weeks.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
The package has been in package.mask since July 2002. Upstream appears dead.
If no one objects, I will drop it from the tree in a week (since it has
already been masked for years anyway :) ).
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT
R Hill <[EMAIL PROTECTED]> said:
> Anyways I just like anything that makes use.desc more useful than
>
> foo - adds support for foo
That's really a completely separate issue. By allowing duplicate entries we
just allow people to put useless information in two places inste
or just something to keep my eye out for?
I don't see this as a groundbreaking change that requires a GLEP or anything,
especially since I eliminated most of the duplicates today, after talking
with the respective maintainers. There are probably only 3 or 4 left.
--
Mark Loeser - Gentoo
nd make sure
they are alright with removing their entry.
On a more global scale, we should decide if this is valid though. I haven't
exactly been convinced that it is useful, but I'm not opposed to the idea.
I'd just like to see a decision one way or another.
--
Mark Loeser - Gen
it be acceptable?
--
Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpmrmdUiVjvE.pgp
Description
ndle switching to something else if
they are using it?
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
Jason Stubbs <[EMAIL PROTECTED]> said:
> On Thursday 09 February 2006 09:30, Mark Loeser wrote:
> > Jason Stubbs <[EMAIL PROTECTED]> said:
> > > It was my understanding that it is needed for the 3.3 -> 3.4 upgrade.
> > > Various packages that will
pendencies.
You need either gcc-3.3 or libstdc++-v3. I don't see forcing either upon our
users to be a good thing. The upgrade doc covers how to do the 3.3->3.4
upgrade, and I think most archs are on 3.4 at this point.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
ed it.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpdH6MEmUfuw.pgp
Description: PGP signature
Jason Stubbs <[EMAIL PROTECTED]> said:
> On Wednesday 01 February 2006 02:28, Mark Loeser wrote:
> > We are talking about completely unrelated versions, not what we are
> > touching.
> > For example, old imagemagick ebuilds sitting around, where the newer ebuilds
>
s are not. We have a security bug open about this
package right now, and having an error about deps in some old version doesn't
really help arch teams at all.
I am all for getting stuff ported, but making things harder for arch teams is
not the way to go about it.
--
Mark Loeser - Gentoo
eprecated"?
Can we put this back to being a warning? It makes things a pain for arch
teams that are trying to mark a completely unrelated version of the package.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT
of our users. Yes, breakage will happen, but we can wait
until its down to a more reasonable value. This huge push to get everything
ported over only started recently, and I think we need more time.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email
to
be "things are known to be broken." It's meant to mean, we think all of this
is ready to be stable, which it certainly won't be in this case.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT or
Luca Longinotti <[EMAIL PROTECTED]> said:
> We elected herd leads, agreed on how to deal with the old-style PHP
> packages
Please don't move the old-style PHP packages back to ~arch. That's just
silly. p.mask them when you want to make people transition.
--
Mark Loeser
stead of generating all of the GCC profiles for every user.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgp0U9HtGxgjW.pgp
Description: PGP signature
there are quite a few of these, so I'd like to know how to handle
them. We need to either make repoman not complain if HOMEPAGE="" is supposed
to be valid, or put "none" in there if necessary.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email
Lance Albertson <[EMAIL PROTECTED]> said:
> Mark Loeser wrote:
> > Chris Gianelloni <[EMAIL PROTECTED]> said:
> >>I completely agree with you here. What Gentoo does is make a
> >>meta-distribution, that one can utilize to build their own distribution
&
Bug" project would be an excellent
> idea to assist in this. We need a body with some teeth to get things
> done in a timely manner. We also need enforcement of some sort to
> ensure projects are active and reporting information on their status.
Sounds good as well. I'd li
(always search for existing bugs of course).
Yea, one report per package please, its much easier.
> I'm wondering if a gcc4 tracker bug might help as Mark was planning to move it
> in ~arch.
Sounds like a good idea. I'll probably make one in a bit if someone doesn't
be
s to ~arch soon, please report all bugs
to us, even if you don't have a patch. I'd like to know of everything that
is broken.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT co
Bjarke Istrup Pedersen <[EMAIL PROTECTED]> said:
> Does this mean that gcc-3.4 will no longer have libstdc++ as a
> dependency? :-D
That is what I hope to accomplish, yes.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT ge
Mark Loeser <[EMAIL PROTECTED]> said:
> 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, yo
sure nothing stable depends on it.
Bug #116253 was invalid due to the user's package.keywords.
Thanks,
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web
in as ebuild. Module is named Tcl::Tk, placed on CPAN, similar to
> perl/Tk, small and easy.
> I'll do all needed work myself.
> Could you please advice whom to contact? Where is FAQ for me to read?
File a bug about this as well :)
--
Mark Loeser - Gentoo Developer
le for a
> particular arch.
>
> Betelgeuse is working on a repoman check for this issue, meanwhile, if there
> are more virtuals planned, please bear this in mind. :)
It makes no sense to make a check to verify what seems to be broken
behaviour. The virtuals should be like any other ebu
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 didn't exactly think about this too much beforehand,
si
appreciate it if
you could put the sys-libs/libstdc++-v3 depend into your package if
necessary.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~h
n sort based off of. So, assuming all security bugs have
the Product or such set correctly, you will be able to easily sort. Adding
additional headers to the emails is really trivial if we need something else
to make our lives easier.
--
Mark Loeser - Gentoo Developer (cpp gcc-porti
6
> arch monkeys have a lot of work on our hands.
Yea, we need to know what is absolutely critical so we can add this to the
ebuild policy if something should not go stable if the problem is present.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n
Mike Frysinger <[EMAIL PROTECTED]> said:
> On Tue, Dec 13, 2005 at 08:02:27PM -0500, Mark Loeser wrote:
> > You are working on a policy, or just docs to explain the issues?
>
> documentation on PIC/TEXTRELs/etc...
>
> the policy i consider a no-brainer, fix TEXTRELs
duces textrels or such, I don't see
the problem with marking it stable personally. The issues listed don't seem
to warrant that.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT ha
was listed above, I'm not sure why we should require that people fix these
issues just to have a package deemed stable.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - h
always avoid them. This should be added to existing documentation
policy so it is somewhere for new devs to know about, and existing devs to
have for a reference.
Thanks
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
ans
you will need to wait for it to get all of the mirrors, which will take a bit
longer after that.
[1] http://www.gentoo.org/proj/en/base/x86/gcc-upgrading-guide.xml
[2] https://bugs.gentoo.org
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email -
's needed here to avoid
> things like Bug 64615.
Yea, I updated my statement on the bug to reflect this. C++ stuff should be
the only thing affected, so this _should_ be enough. Its also already
something that's been in the ebuild for a while now.
--
Mark Loeser - Gentoo De
w.
As for a doc, look at: https://bugs.gentoo.org/show_bug.cgi?id=102876
I'm hoping we can get something thrown together relatively quickly so I can
mark it stable. Nothing is going to be required immediately from the user
though, since their compiler won't be changed to 3.4 until they do s
ly
upgrade is available is what we are looking at.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.c
-3.4.* will not be selected as your system compiler after merging it. The
old gcc profile is still valid, therefore it is kept. Users have to
consciously go and change their profile to change their gcc, so nothing is
going to just magically break.
--
Mark Loeser - Gentoo Developer (c
Mark Loeser <[EMAIL PROTECTED]> said:
> Only thing I see
> as lacking is we might want to get a doc together on how to properly upgrade
> your toolchain so we don't get an influx of bugs from users that have a
> system half compiled with 3.3 and the other half with 3.4 so th
stupid
mistakes users could make.
--
Mark Loeser - Gentoo Developer (cpp gcc-porting toolchain x86)
email - halcy0n AT gentoo DOT org
mark AT halcy0n DOT com
web - http://dev.gentoo.org/~halcy0n/
http://www.halcy0n.com
pgpgktGju3Vxt.pgp
Description: PGP signature
they remove it though, libstdc++-v3 should be pulled in
after that. Only issue I really see is people that have libraries compiled
with 3.3 and 3.4 and don't know why stuff is broken. I don't know how large
of a problem that will be though.
--
Mark Loeser - Gentoo Developer (cpp g
This is basically a heads-up email to everyone to say that we are probably
going to be moving gcc-3.4.4-r1 to stable on x86 very soon. If any of the
archs that have already done the move from having 3.3 stable to 3.4 could
give us a heads up on what to expect, that would be great. Only thing I se
Ned Ludd <[EMAIL PROTECTED]> said:
> I really can't give an accurate example. Halcyon who has been testing it
> merged world and he was yeilded with 18M of debug info (I have no idea
> how many packages he has).
Just for the sake of reference, this was with 95 packages and CFLAGS="-O2
-march=pent
If no one steps up to maintain it, luabind will be removed from the tree in 2
weeks. It has not had an upstream release since 2003 and is broken with
newer versions of boost, >=1.32. Nothing in the tree deps on it, so there
shouldn't be any problems with its removal.
Thanks,
Mark
pgpG2gGPCKLN
101 - 200 of 212 matches
Mail list logo
