Re: [gentoo-dev] Gentoo Council 2008/2009 Nominations end TODAY 23:59 UTC
I think tsunam and kingtaco are the same, but I'll wait for them to make those statements themselves. While I thank those who nominated me, as in past years I've declined the nomination in favor of working on other possibilities. I wish those who are running the best of luck. So yes I decline the nomination. -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for April
Wulf C. Krueger wrote: On Wednesday, 02. April 2008 22:46:16 Petteri Räty wrote: How does having the average time between commits be at most a week sound and if it goes under that, undertakers will get a notification? It sounds like you're trying to get rid of someone. - !DSPAM:47f3f2be39031804284693! Yep its me! Seriously...we don't need to be paranoid people. -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Help offered - Portage tree
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fabio Erculiani wrote: | Hi all, | snip | Cheers interestingly enough ixnay...I've tried contacting you about working together with Gentoo and on things related to eapi as sabayon is one of the more popular distributions that has somewhat of a basis on Gentoo (I've tried approximately 3-4 times in the last year or so) . Every time I tried from 4 different domain accounts including my Gentoo one I was denied the ability to send you an email. While I'm sure many comments are going to be a bit harsh if realistic please do feel free to talk to any of the developers. Splitting isn't really realistic as that is getting away from upstream. As an organization we try to maintain the same way as upstream intends. If they say that mysql is not a collection of server, client then its just mysql. Xorg is a perfect example. It was a huge package, that got split up. It took Donnie and the rest of the X team a while to get everything ready for the tree but we followed upstream in having individual packages for the different aspects of the larger project. Please feel free to contact me directly if you wish -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH2aop2ZWR0Jhg/EsRAkppAJ0e5u5LEfrdHP/FpsgghMm0kd07mQCfRmZP 3rMibnJCkKJih3bsz/VYGpY= =c41u -END PGP SIGNATURE- -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Help offered - Portage tree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio Erculiani wrote:
| Hi Joshua,
| I never had issues with my emails. So I don't really know what to
| answer you regarding to your issues :)
| SPLIT: Although I think it can be a suboptimal thing for us, I can
| understand your policy. Let me add that, to me, the biggest issue is
| about (R)DEPEND. Splitting packages and maintaining in an overlay it's
| not that hard.
|
|
|
I personally have no desire to follow the redhat/debian/other binary
packaging systems which split up infinitesimally small packages. It
causes a lot more busywork in my opinion then any potential benefits
that it gains you.
As far as the depend issue you mentioned: Having both Rdepends and
Depends isn't as far as I'm aware part of any EAPI currently (Correct me
if I'm wrong people). Rdepends are needed for the builds so you will
often see either RDEPENDS=${DEPEND} or vice versa. If its not there then
its more of a matter of accounting then anything. I would think, and
correct me if I'm wrong again, that it would make sense that if you only
have RDEPENDS or DEPEND, then those same applications are required in
the runtime of the application. Does it need to be explicitly stated? So
far the three package manager that I'm aware of all manage this fine.
Those being portage, paludis, and pkgcore. If there are other package
managers out there that might have issues Its a perfect example of a
reason to be involved in the EAPI discussions to help define what is
needed and where.
So what I suggest to you is perhaps looking over the EAPI=0 draft
documentation and proposing some additions and or modifications that
benefit everyone (not just one person), as its designed to be a standard
for anyone who makes use of ebuilds and beyond.
http://dev.gentoo.org/~spb/pms.pdf
Is the current form, but halcy0n is working on an updated version of it
for the next council meeting.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH2bL22ZWR0Jhg/EsRAkduAJsGBKKl5HgR5YXziPn9yOLbi5F5MwCfacIC
b/aqsokP3A6JFJ7hO4LGNXY=
=BGqi
-END PGP SIGNATURE-
--
gentoo-dev@lists.gentoo.org mailing list
[gentoo-dev] Google SOC 2008
All, Google is once again doing the summer of code for students. I'm helping organize it this year and am putting out a call for some elements to help. 1) We need idea's for things to do. Diego has already submitted some via his blog which have been taken into consideration. 2) We need mentors, so far confirmed I have: Diego and Saleem -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Google SOC 2008
Rémi Cardona wrote: joshua jackson a écrit : 2) We need mentors, so far confirmed I have: Diego and Saleem What kind of work is involved there? I wouldn't mind being a mentor but I'd like to know a bit more about what's expected from a good mentor. Thanks, Rémi There's a few requirements. Being decent in a language or multiple languages would certainly be a plus, as the students are writing code. having someone writing something in C or C++ when you've never touched it wouldn't exactly work out that well obviously. Having time to interact with the student as well. They are getting paid as are we as an organization, so helping them and giving them idea's is needed. Touching base and making sure they are still progressing on their projects. Its summer...but they are being paid to work so it is a job as I hope as a mentor you would take a similar approach as well. Basically you act as a technical boss/mentor/leader to someone. One area I'm working on for this year is goals within the overall goal that can be implemented hopefully even if the project isn't fully finished before the end of the project. For the mentor it won't be a full time commitment but having time to talk with/help someone with their project and explain how to implement this feature or get this information from Gentoo's system would take some time. As a warning some people come on board with excellent programming ability that you don't need to do much with/for. Some well its their first real jump into programming and need more attention. I plan on having a few additional questions for the Gentoo related applications to help define that kind of thing and hope to get people together in such a way. As well a few of the people who are helping run it have agreed to help poke/get updates from the mentors and step in and help in whatever way possible to the students as well. Basically, we want as many projects to succeed as possible and become a daily tool or vastly improved tools as possible. Its certainly something that is possible. -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] 2008 Google Summer of Code
Grant Goodyear wrote: Google has been hinting not-so-subtlely that there's going to be a 2008 Google Summer of Code. I expect that if we want to participate, we're going to have to have our ducks in a row by March, if not earlier. So, does Gentoo want to participate this year? If so, who's going to run it? Who's going to help? What are we going to do differently this year? I'll help if it's something people want to do, but I'd like to see some serious changes this year. I'd like us to only accept proposals that we actually think are quite good. In the past we've been told that we have N slots to fill, so we choose the best N proposals, despite the fact that we often only get a handful of exceptional proposals. I'd also like to see us require weekly public status reports from our students. Quick show of hands: how many people know how what any of our students accomplished last year? I doubt there are many, despite the fact that some good work was done last year. Thoughts? Comments? -g2boojum- !DSPAM:479f440c189611018716084! That's one of the things that will be discussed at the upcoming User Rel meeting... -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] 2008 Google Summer of Code
George Prowse wrote: Grant Goodyear wrote: Google has been hinting not-so-subtlely that there's going to be a 2008 Google Summer of Code. I expect that if we want to participate, we're going to have to have our ducks in a row by March, if not earlier. So, does Gentoo want to participate this year? If so, who's going to run it? Who's going to help? What are we going to do differently this year? I'll help if it's something people want to do, but I'd like to see some serious changes this year. I'd like us to only accept proposals that we actually think are quite good. In the past we've been told that we have N slots to fill, so we choose the best N proposals, despite the fact that we often only get a handful of exceptional proposals. I'd also like to see us require weekly public status reports from our students. Quick show of hands: how many people know how what any of our students accomplished last year? I doubt there are many, despite the fact that some good work was done last year. Thoughts? Comments? -g2boojum- How does the SoC work within Gentoo? Do the developers suggest things they want worked on or do the users suggest things, the developers okay it and then they get worked on or what? George To give a short answer, its a combination of projects suggested by developer and projects submitted by the students. They get reviewed by the User Rel/SOC Staff and put into an order of projects to submit to Google. They then decide which ones they approve of to fund for the students to work on. Ultimately its up to google to decide on the projects and how many get funded but we as the project have some say in the order they view them in. This year I'm hoping to get some decent projects that are attainable in the summer for students. We've had unfortunately some that have gotten fairly far but didn't get finished. This will also require mentors who work with the students who can help them succeed as well. Its something I'll be bringing up soon as well to discuss with the developer pool (as my understanding is that at least one mentor must be part of the project), doesn't eliminate mentors from the community but it'd be 2 instead of just one I need to go over more details about it but would like to apply again as a project. -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Nominations open for the Gentoo Council 2007/08
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Blackace wrote: I'd like to nominate: vapier tsunam nightmorph seemant avenj christel Although most of them will probably decline, I think they would do an excellent job straightening out Gentoo's heading and have the barnacles to perform the requisite keelhauling. Thanks, Blackace. -- !DSPAM:468e8e97303331804284693! I'm declining as well. Not sure if everyone got the message elsewhere so... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGoPly2ZWR0Jhg/EsRAgulAJ0Tnyy2BnfL3f/yhW57QDxI60gS8gCeNkNz 5iCiWuArvnGBVZBqXiKImv8= =KYqB -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] net-im/pidgin protocols
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jakub Moc wrote: Petteri Räty napsal(a): Or just do it via package.use in profiles until IUSE defaults are implemented. Regards, Petteri As noted before, they are implemented, just not allowed in the tree. Plus, what vapier said, this info belongs to the ebuilds, not to profiles. Wrt pidgin - seriously, what's the big issue here? Users can't use emerge -pv output and determine what they want, or? Will we bloat the profiles everytime someone forgets to enable a flag and goes complain upstream about a 'missing' feature? -- !DSPAM:469f3b40137571336712104! Honestly..this is not something to get picky over jakub. Upstream was nice and actually came and politely asked us to change the defaults to what most people would consider sane (all protocols by default). As I think most people emerging pidgin..would like to use any protocol by default..not go..hey I don't have yahoo, I should check my use flags. Which obviously hasn't happened as users pop up in #pidgin to ask why the heck there isn't a yahoo account available. This should be a nothing change to do. Its also working with upstream and maintaining some good relationships here..and or help improve them in general. That should in fact you know...be part of our goalsto improve communications between Gentoo and other projects. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGoN572ZWR0Jhg/EsRAgc6AJ0VsBkFjPd2oeL3rf5omoNApx7UfwCfaw2T 1MaeNz8c3tGAnJ4bDQ/J9as= =hmCp -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Last rites: media-tv/freevo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Buchholz wrote: On Wednesday, 11. July 2007 21:28, Stefan Schweizer wrote: Hi, # unmaintained, masked for removal, bug 156497 # You can find a new version in the sunrise overlay media-tv/freevo-1.7.2 I'll take over (proxy) maintenance of it, beandog (media-tv) agreed to lend a hand and we have _AxS_ from #gentoo-sunrise for the rescue who already committed the ebuild there. Moving it over to the tree as soon as I have a closer look at it. The package.mask for 1.7 stays. Robert I might not use it, however its good that one of the two main vdr applications is staying in the tree. Thank you for taking up the maintenance on it Robert. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlVJ42ZWR0Jhg/EsRAu5vAJ9Jegk0/n2rhqOX7hYBfs/+va1mkwCff2Y9 EXFXqifQF5xYiq4R2oJ/kfA= =PRMQ -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Call for more photos on planet.g.o
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rémi Cardona wrote: Hi everyone, [snip] Rémi Does that mean that my tophat = funky picture of myself? if you have no clue which I'm talking about.. http://planet.gentoo.org/images/tsunam.png isn't that however the point, to have fun with it? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlWUo2ZWR0Jhg/EsRAhsKAJ9Q6aWi6jfuRu2DLfUzDOe5paBoJQCfdYcB LSqgzmFy+e6iOjM8l3gN6mE= =ihuG -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Re: [RFC]: gentoo-politics ML
Benjamin Judas wrote: Am Dienstag, den 12.06.2007, 22:44 +0100 schrieb Stephen Bennett: On Tue, 12 Jun 2007 23:10:32 +0200 Benjamin Judas [EMAIL PROTECTED] wrote: ...which means that he has a documented history of trolling not only on mailinglists but also in irc-channels; not only against developers but also against volunteering users. So do most people on this list. Stealing a single lollipop doesn't make you a villain. Continuously running amok and shooting at people for years does. !DSPAM:466f1486294802542615845! Can we possibly get back onto whatever the heck the topic might of been...else this just is going to prove that we don't know when to take things from the mailing list to just emails to individuals... signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] 1/2 OT: splitting packages
Daniel Ostrow wrote: On Mon, 2007-05-14 at 23:18 +0200, Enrico Weigelt wrote: Hi folks, I know this issue is not actually in the scope of this list, but maybe some of you might be interested: Lots of packages have optional parts which (IMHO) should/could be their own packages, ie. GUI frontends to console tools (aumix) or several language bindings of certain libs/toolkits. Those things tend to produce circular dependencies, which can only be solved with tricks like multiple builds, special useflags like build or bootstrap. For example berkeley db: it written in C and has additional bindings for C++ and Java. This produces two kind of problems: a) for the base system we must take care that it's built w/o them. b) if some package needs an special binding, dependencies get tricky (AFAIK portage cannot solve feature deps yet) An clean solution would be having the bindings as separate packages. Of course, often the upstream is not ready for this yet, and it's not in the scope of an distro like gentoo to such heavy changes. But those splits really should be done (IMHO) to make things a lot easier. So let's do it - do the split and try to convince the upstream to get it in. We release our packages as upstream intends. If they don't split them, we don't split them, talk to upstream not us. This is what use flags are for... --Dan At what point is your sand so fine that you can't identify it as a grain. In other words...this induces a much larger set of packages that at least in my opinion would waste a lot of developer time for not a lot or any benefit, and as mentioned by Daniel we follow upstream and if they want it as one large package, we'll do it as well. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Planning for automatic assignment of bugs
Nguyen Thai Ngoc Duy wrote: On 4/26/07, Robin H. Johnson [EMAIL PROTECTED] wrote: Case 2 - Metadata contains a single maintainer -- - The herd field is not used. - The maintainer address is used as the bugzilla assignee. This is important for all the herds that have aliases that are NOT the same as their herd name! This diverges from existing manual practice, to avoid unnecessary duplicate mail, and means that existing metadata may need a cleanup. It should take devaway into account. why? Seriously, dev-away != dev retired... having it take devaway into account is pointless in my opinion as it won't improve it being properly assigned...as it'll be covered in other cases, and its not like there's not bugs for all of us dev's that have not sat there for a month or so, at some point signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [ANN] Multiple version suffixes illegal in gentoo-x86
Ciaran McCreesh wrote: On Wed, 25 Apr 2007 09:57:39 +0200 Danny van Dyk [EMAIL PROTECTED] wrote: Funnily enough... If we're going by PMS drafts, that's illegal whereas multiple suffixes are legal. PMS permits multiple suffixes, but limits any individual version component to eight digits to avoid problems with integer overflows, floating point precision etc. And when PMS specifies that together with a proper way to compare multiple suffixes there will be no problem. PMS *does* specify a proper way of comparing multiple version suffixes (and version specs with a leading zero for that matter). I'm not particularly happy with the wording, but as far as I can see the description is at least correct, even if it isn't clear. Alright guys, This is enough. PMS is a work in progress its not going to cover everything that users and developers are going to be in some cases boneheaded enough to actually pull off (always have edge conditions). We're continuing to downgrade here and quite frankly the discussions seem be getting into tangents more then the actual topic at hand (you know...the fact about what the proper suffix format is), and that is up to the council to decide. If you have issues with the council, bring it up in the proper channel, as others have mentioned where its at. Now either get it back on topic, take it to private emails to discuss between yourselves, or take up the issues that relate to the council, to the councils mailing-list/members. They are actually you know...alive and willing to talk to you. Annoyed proctor out signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [ANN] Multiple version suffixes illegal in gentoo-x86
Ciaran, You missed the bandwagon on trying to use the conspiracy theories phrase already. That happened a full 24 hrs ago. I'm sorry you were off-line. Next time try to come to the party on time, otherwise keep quiet. Already been handled as its offtopic, please just let this one drop. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: File collisions
Rob C wrote: On 19/04/07, *Christian Faulhammer* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Steve Long [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: On the issue of QA, I think enabling FEATURES=collision-detect by default would do a lot more good at this stage than test. Arch teams normally have collision-protect enabled when doing keywording/stablingin my eyes this is sufficient. V-Li Its obviously not, Many users are reporting file-collisions on a weekly basis. So either this isn't sufficient or the arch teams are not acting as you describe. -Rob Rob, Please watch it when saying that the arch teams are not acting as described. I can tell you that we catch what comes to us. We don't get every single package pushed on us as some never go through stable testing, and we don't have every single package installed(that's unrealistic). If they do then if there is a collision a note is filed in the bug and we wait for a fix, as it actually does bail you out of the build. This has been the mantra of at least x86 since the creation of the team. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] New Developer: Christina Fullam (musikc)
Christian Heim wrote: It's my pleasure to introduce to you Christina (Chrissy) Fullam (also know as musikc on IRC) our latest addition joining Developer relations, more precise conflict resolution and will probably join Chris' GWN minions. Christina is joining us from Greenville, SC (that's in the southeastern part of the USA) where she's currently working as an IT manager with social skills for Erwin-Penland. When Chrissy isn't around computers (which she is most of the time), she's trying to pet Chris (yeah, wolf31o2) and her other pets (like cats, dog, ferrets); reading weird books (like 'office politics') and rearranging her desk (sorry, Chrissy 3). So please welcome Christina as a new fellow developer among us ! Regards, Christian Oh goodie, I can flirt with wolf's woman now too :-D *ducks* signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] EAPI 1 (Was: Re: Monthly Gentoo Council Reminder for April)
The arch teams have been pushing for this for a long time. They're trying to get this enforced, but are having limited success because there's no way for FEATURES=test to become widely used that won't lead to broken user systems. Moving src_test to be always on in future EAPIs is an easy way of helping arch teams achieve this goal without breaking anyone's system in the meantime. Erm, no I have not at all (speaking as a project lead for x86). Test is not viable for a lot of reason as being on by default. One that I can come up with off the top of my head is php. The test suite for it makes test inadvisable on any desktop system, I'd say the same for a server as well. Not to mention that a lot of upstream test functions are in fact themselves broken because they require dependencies that are not required for the application itself. This is not a simple case of downstream (being gentoo) doing this. There has to be quite a bit changed for test to be viable and even then I don't think it really is unfortunately due to test packages that can take 12+ hours on a decently equipped modern system. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [RFC] New metastructure proposal
Petteri Räty wrote: Alexandre Buisse kirjoitti: What I *want* to do is to make gentoo fun again. And I believe that decentralising and giving more autonomy to people will achieve exactly that, for reasons explained in the proposal. I am a project lead for two projects and have no idea what kind of more autonomy I would need for my two projects. Regards, Petteri -- Gentoo/Java project lead Gentoo/Recruiters project lead I agree as a Project lead of another...I don't think more autonomy is needed..Basically I'm allowed to do what Is best with the team (and that amounts to mostly just patting people on the back. Good job x86 team members btw ---see there's a pat on the back). So really, I think most project leads are there to a, give a direction to the team, and once its there twiddle our thumbs and go yay I got good people under me who work hard. its management at its finest ;) signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] *DEVELOPMENT* mail list, right?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Cummings wrote: When you pop into your mail client of choice and find 50+ unread messages in the last few hours, you know what kind of day [EMAIL PROTECTED] is having. Don't suppose we could get on with that silly topical thing of development? Surely there's a usenet channel where you can discuss conspiracy.gentoo at length? Or at least take it to the user list? /me stretches and blinks So, fellow devs, what's new with development? For those interested, genlop has migrated into gentoo as a project with the permission of upstream, which no longer maintain it. Um...any new tools or projects people are working on? Anyone? I'm working on figuring out how to fix things I don't maintain (stupid lack of graphics *bonks the app*)..and trying to get motivated to deal with a package that has a nasty install to be upgraded to a new version. Does that count? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGFYVxSENan+PfizARAlASAJ91A85lHSoocCZHpQACxBJZZ4BaWACdHC33 ufXQQonw7lFh3G5hVORYiGs= =oyCR -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Hiatus (sort of)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Petteri Räty wrote: Paul de Vrieze kirjoitti: Hi all, Me and my wife and son are moving to Australia. We are now waiting for the visa's to arrive, and after that will need some time to set ourselves up. Our computers however are being shipped as we speak and will only arive in australia after roughly 6 weeks. I'm looking to buy a laptop, but connectivity will be problematic anyways. As such I will not be able to contribute as much as I would like. Paul So I am guessing this means that we are free to touch your packages? I think betelgeuse really wants to touch your packages -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGDY53SENan+PfizARAkXHAKCGGIlcObUdrP4E6w9Y8scWBgB5yQCfSey4 hLiYokWJiNIQAv0kRZyvKoQ= =zrqg -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Another council topic for Feb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Doty wrote:
We're going to talk about arch keywording policies. IMO we should have
a standard policy if you own and use ${ARCH} then you may keyword your
packages for ${ARCH} with the exception of the sys-*/ categories.
Speakup now to get your input in.
This is a horrible idea hearkening back to the problems we had a long
time ago. The stable tree's were broken messes that were that way
because developers ran ~arch but tested an app they wanted stable and
as long as it ran it was marked as such. I will protest any kind of
arch kerwording to the hilt. If you want to mark something ~arch and
have the arch that is fine with me. However this entire plan will kill
the arch teams that have not only improved the stable trees, they have
proved to be a valuable tool for recruiting, as both the x86 and amd64
team have have a 60+% ratio of arch testers becoming developers.
In other words *smacks everyone with the protest sign*
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFxrQtSENan+PfizARAuSeAJ9l0Q52YtM6OCLQbdtjsU81xVEc6ACfVAbM
jC3QdD5ww2yPJZ3CVYN4MNw=
=6gdH
-END PGP SIGNATURE-
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Retirement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon Portnoy wrote: I've been mostly inactive for a good while but hanging on mostly for sentimentality's sake, it's past time for that to stop. I mostly only maintain a small handful of ebuilds, I'm sure they can find proper homes quickly. None are maintenance-intensive. And of course, the only thing anyone is really concerned about; robbat2 has already laid claim to fortune-mod-gentoo-dev ;) Later. It's been fun, it's been real, but it hasn't been real fun. :) I'll be around #gentoo/#-dev. As I was gone for a week I didn't see this til this weekend, via seemant's blog. I was good and didn't reply til today to take that full week off. I'm sad to see you go Jon but know that you will continue to do great things so good luck in whatever you end up getting involved in -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFT24/SENan+PfizARAlwKAJsGIO7aKq5jmYGJp1G+WkidrBBcKACggzZV nc7glXTmCi8Bv5jkT7bbFpE= =/KWb -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Beryl maintainer needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Böck wrote: Hi, As you may know, beryl is a fork of the famous window- and composite-manager compiz (beryl formerly was named compiz-quinnstorm). I'm maintaining the compiz package and at first thought I'd also take beryl, but I'd prefer if someone else could take it. My personal opinion is that I don't really see the point of this fork, but there are many users out there that seem to like it. There are already testing-ebuilds of beryl in the coffee-overlay (www.xgl-coffee.org). There's a guy with the nick nesl247, who regularly hangs out in #gentoo-xgl on freenode that wrote those ebuilds. If any Gentoo dev wants to take care of beryl, please take bug 150033. You should review those ebuilds in the coffee-overlay together with nesl and then add them to portage. cu, Hanno ([EMAIL PROTECTED]) I can think of one reason...it doesn't depend on a ton of gnome stuff ^.^;; -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFNAXiSENan+PfizARAhsoAJsHyrTSznDFI0iFWs4HpKL4yjRKAwCfYKyE V1MtT7JJxndMIfh9xHKWSOk= =rCa9 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] New Developer: Jeffrey Gardner (je_fro)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Ramsay wrote: Petteri Räty wrote: He has played bass guitar for 20 years or so. Considering that he has been doing it before I was born, one would think he is some kind of an expert but maybe he is just modest when he says that he could be a LOT better. Excellent, another member of the soon-to-be-famous Gentoo rock band! I think Joshua Jackson (tsunam) has already volunteered to be the singer :) What is it, three new musical devs so far in the last 2 weeks? Ack! we want people to come to gentoo not scare them off _ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFJtQoSENan+PfizARAqbTAJ9FmxDh4VDjfC17yJjwJeCVNqzNigCeOvFo tOaDo9Q4Bjo/T8XSKOyGjoM= =EPWm -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] RFC: Last rites for $package ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Weigelt wrote: Hi folks, snip To be perfectly honest, we're not going to hold someone's hand with this. We shouldn't be expected to. A package will be in mask for a month before its removed. That's a good warning sign that something is up. You can view the package mask file and see the reason behind it, as well you have this mailing list where announcements about what is masked and when its removed. If people can't find the reason from all those sources of data..then quite frankly..there's a larger issue going on with them. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFHDUySENan+PfizARAk/eAJ4jHTvqjjWBHFSgY24Wkb3XTits3QCfVgUz JOj/wWgWBaCVxVyfeh23PKM= =1IPj -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] New dev: dev-zero
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Stelling wrote: Hi all, It is with great pleasure that I announce the devification of Tiziano 'dev-zero' Müller. He writes us: I'm from Zurich, Switzerland. Born here and still living here :-) I'm studying physics at the University of Zurich and working in a small company as IT responsabilitee and software engineer. I also worked on a subproject of the LHC (Large Hadron Collider), called LHCb. I'm responsible for the database design and implementation (postgresql) for the sensor test database. Besides that I'm working as a freelance software consultant for a couple of private customers. If I'm not working, I'm playing the violin or watching movies. With this addition, the Swiss conspiracy soon will be powerful enough to bribe everybody else with chocolate, so you better watch out. Everybody please give Tiziano a warm welcome! Another one for the band...get someone with the drums and you could make a folksy old world gentoo song *interesting very interesting* oh and chocolate! if its in fact white chocolate which isn't real chocolate but thats something for another time. Welcome aboard. I think this calls for a beer and chocolate party (any excuse ;) ) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFGvKxSENan+PfizARAhnGAKCMXxRFZ0746kpw8NCVDaWiub8csACfbQiF a4zadOaY05duZHVmiwV/+fo= =Bbfy -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] New Developer: Tristan Heaven (nyhm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Stelling wrote: Hello all, I am proud to announce Tristan Heaven as the latest addition to the Gentoo developer community! Heaven knows why he wants to contribute to Gentoo: To help the games herd maintaining the games-*/ categories. Tristan is 19 and lives in a small town in England, near the Lake District. In his free time he is mostly busy playing^W_testing_ games, so we can all be assured that any stablization requests filed by him have gone through a careful inquiry. Welcome Tristan! Oh goodie another person who just likes to act like a developer but really wants to just play games like Wolf. *wink* Welcome aboard Tristan enjoy being a slave to the people now MUAHHAHAHAHAHAH. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFGVFjSENan+PfizARAq8nAJwNYozco4YgKVaufMBZvEXDuUI7/gCfQygH UbXRL1V1EmWafGNdryyaHbg= =6HLE -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] seeds, GLEPs, and projects
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Stelling wrote: Grant Goodyear wrote: If we (being Gentoo) say that we're going to do something, and then things fall through, it might make us look bad, after all. Maybe it's just me being stupid, but what exactly do we have to loose? (This is a serious question, I'd appreciate serious answers.) Well, I'd probably say. The respect of others both in and out of the open source community. Secondarily I'd say that we lose a bit of the corporate ready appearance that some are working towards (which I don't oppose). Third, we lose the respect of each other in the project. Seriously, its not something to be thought of lightly. If a project you announce fails, people will remember oh Simon started so and so, and it failed utterly. /me considers these to be serious replies ^.^;; --the face however isn't *wink* -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFEvAUSENan+PfizARAmQ7AJ97BwzV4MNl9PRAmOsGqFf9N0DgvwCeP4rS 4TeCV+6i3Zus8sufzz4LN0k= =tIif -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Gentoo 2006.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Edgar Hucek wrote: Apeal on extended testing : Developer, please test things more carefull before you release it. I already found things which does not compile out of the box. 1.) Use wacom does not compile out of the box. You have to unmask linuxwacom. 2.) Enable the use flage accessibility gnome cant be merged. It fails on compile the speech-tools. It seams that USE flags are not realy tested or how can it happen that there are already know bugs in the stable distro ? http://bugs.gentoo.org/show_bug.cgi?id=116030 Festival and the speech-tools are well know not to compile with gcc =4. cu Edgar (gimli) Hucek Well, thank you for your concern Edgar, however in the future would you please at least look at all the work that went into the release of this. There were months of testing by the releng team in association with the arch teams to ensure that as much was ready to go. I'd like to also point out a few people who went above the call on x86 to get things filed. Ryan Hill (dirtyepic) filed many many many bugs as blockers for 4.1.1 going stable at my request. The Archtesters for all teams as well worked very hard testing things to make sure they worked as w ell. Before it went stable, almost all were stabilized if they could be. There are a few packages not ported yet in the games category but we weren't going to let that stop the progress either. Quite frankly saying that we didn't do enough testing, is a insult to everyone who worked on this release. No release is going to be perfect for us as a project, what we have attempted and I believe been successful with is making the transition as painless as possible. ~Joshua -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE+es0SENan+PfizARAmeFAJ9cNsqzCtlU3KRu225GB5I1Yz+RGACdElH+ uOxr1Zx35l/K1i6CLeYmpHA= =AZjO -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Gentoo-Status
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Seemant Kulleen wrote: Your concerns are well noted. The trustees in general are quiet even amongst themselves, but I hope this changes with the new board coming in next week (ish?). It's been my idea to propose that someone (tsunam was in my head) publish a trustee monthly news or something. The one I'm curious about is the council -- the council posts to -dev before and after every meeting (and puts meeting logs up on the website within days of a meeting). I suppose the webpage itself could be updated, but I'm unsure what else the council can do. Perhaps you have some ideas? Thanks! Oh, even more reason to poke the trustee's! *grins evilly and starts singing* Its so easy when your evil. To the gentleman, I'm Miss Fortune To the ladies, I'm Sir prise I'm the fly in your soup I'm the pebble in your shoe I'm the pea beneath, your bed that makes you wriggle and writhe In otherwords I'll do it :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE6kvWSENan+PfizARAi/YAKCEUFnczXjgQf8UxnjRXP9aup+UOACfdacH +vUC4GUwn4Wg7ABmtLqQ6kM= =FAoG -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] [treecleaner] Last rites: media-sound/alsaplayer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Doty wrote: Christian Heim wrote: The media-sound/alsaplayer package is pending removal as requested by [EMAIL PROTECTED] for multiple buffer overflows [1], dead upstream [1] and a crash occurring when playing uLaw/AU Audio File [2]. The package is currently masked and is pending removal on 15th September. [1] https://bugs.gentoo.org/show_bug.cgi?id=143402 [2] https://bugs.gentoo.org/show_bug.cgi?id=143742 Flameeyes is afk at the moment, but I know he usually maintains this. aye he does and its been discussed before. I at least talked to him about it, the problem is that alsaplayer is a self contained product that nothing else truly fills the shoes of. Other things are simple but they depend on a lot more..etc. Its just a funky little app that no one has really replaced. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE6PJVSENan+PfizARAn+2AKCTwsB1ZzWglhF0hxa0dCQvSCEqOQCfU79M qJ50q/A78XJpXw5qnH+0qf0= =MKaQ -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] RFC: AT emerge info cruft attachments to [STABLE] bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ex.
gcc 4.1.1 works on x86 with the following:
USE=gtk nls -bootstrap -build -doc -fortran -gcj -hardened -ip28
-ip32r10k -mudflap -multislot -nocxx -objc -objc++ -objc-gc -test
-vanilla
Looks OK to me. But hey, aren't arch devs and testers alike supposed to
test (almost) all flags? And also, wouldn't you also want to know about
FEATURES, specifically FEATURES='{test,collision-detect}'? How about
KEYWORDS? You would still need to be able to find the full `emerge info`
in an attachment, I guess.
Heck no, I'd spend a few weeks just testing for example php. That's
deranged at its best and insane at the worst. The request as put out
to the arch testers is to use the system like they use any system,
just that they only run x86, amd64 other packages except for what they
are going to be testing. As far as features go we ask that they run
the same as a developer should, test collision-protect on top of what
is already added by default. Keywords is not useful for the arch teams
as we know that the AT's run $arch and not ~$arch. However at least
saying x86 okie with me here would be a requirement
I still think failures should be reported in separate bugs, as they are
likely to cause lots more information to be passed.
Kind regards,
JeR
Actually, one thing that you might not know is that quite a few of the
archtesters are capable programmers, they've tested a build that
failed and went about submitting a patch that would fix the issue
right there on the stabilization bug. Now you might want to say why
are they not developers yet. Part of that is probably, because they
haven't been approached by a developer yet, the second is that some
can't dedicate more time then what they are doing currently to help
the project, and that is alright. They are helping the arch teams
immensely and I'm thankful for them taking their own time to be doing
what they are doing. I might not always say thank you on the bugs,
however I feel it everyday.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE3K8uSENan+PfizARAlacAJ4mb/pTvX119A+41a0qVG8SE3IrcQCfaOSn
iMxOOBGJCXGxZfU+4BeB3Zg=
=fbsi
-END PGP SIGNATURE-
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Update notes on -p ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Weigelt wrote: Hi folks, some packages print out important notices on install/update. I'd like to see those notes before actually updating, so when using --pretend. I'd like to see this as an feature. We could put those texts into some ebuild variable or an separate file, so emerge can show it on emerge. Yes, I tried --changelog with several packages, but it actually didn't show up anything. And I'm not sure if the changelog isn't too much text for the user - I only want those things, which today get printed out as important notices while/after emerging. cu Another option is to use the new elog feature in the 2.1 portage, if you look at the make.conf.example, it'll explain how to use it. Its quite useful even if its after the fact, but you won't miss them at least. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE2PtpSENan+PfizARAtFRAJ0ZHuNzjvfn6elk5wWUDv/CqANWKACcDZ1V MKzvxhW+DMqL6qEgPgPEz5Q= =YZvV -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: app-doc/chmlib - call for maintainer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Hill wrote: Raphael Marichez wrote: app-doc/chmlib is without an active ebuild maintainer and has an open security bug [1] Anyone willing to take care of this package in the future, please update metadata.xml and CC yourself on the bug. [1] https://bugs.gentoo.org/show_bug.cgi?id=143181 if no one else takes it (and i sneak by the recruiters ;)) i can. i use it daily and follow the ml. --de. Gasp! my mentee isn't in the sea like a good mentee should be *gets out the cow tazer* Back you go back to the sea and holding your pole for the oil companies. Glad you want to take things on though :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE2SvDSENan+PfizARAu8+AKCTeY3LaZnLkmIvKppAW6eIdNKD4ACdHuA/ x+US03hZSmnDyLTvDIQPW4g= =1ISG -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Developer Upgrade! Steve Dibbs
Christel Dahlskjaer wrote: Hi all, It is with geat pleasure that I can knight Steve (aka beandog) a 'real dev'. Under Mike (KingTacos) hawkeyed glance I have recruited my first recruitee (hmm, it's not really called recruitee is it?) and am embarking upon a joyful^Wstressful time as a recruiter.. Enough about me (although being female I feel compelled to try steal the show..), most of you already know of Steve as he has been with the User Relations project as our Planet monkey for a while and is also heavily involved with the larrythecow.org/net community project, and of course from his contributions to the GWN. He will now be joining in with antarus' efforts of bleaching^Wcleaning the tree as a QA tree cleaner and I suspect he will be slaving away with the media-video herd. I wouldn't be surprised if we see him infiltrating other projects too, I'd urge the following few projects to look out; AMD64, media-tv and Knowlegde Base! So yeah, bottoms up for beandog! (No, not that sort of bottoms Chris White..) Christelxx He's also volunteered to help out on the x86 project as well. I swear I didn't push him off that cliff in any way. *wink* welcome aboard...now you just need to go insane to be truly one of us -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for August
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lance Albertson wrote: Curtis Napier wrote: I got to chat with the CEO of the company that donated that equipment and the wait was *more* than worth it. Once it's up and running our bugzilla will be rock solid and fast fast fast fast fast for years to come. Well, as I stated before. Having nice hardware will help a lot, but if we could get upstream bugzilla folks to fix some of these issues instead of us having to resort to a clustered database structure would be the better solution in the long run. A fast db cluster/web server means nothing if the database structure behind the app isn't done properly. It might be worth it for someone to maybe look at the problem in the code and see if we can patch it from our end and then submit those patches upstream. That approach generally works better. But I fear that the change needed to be done on it might involve so much change/work, it may not be worth it. Who knows, maybe its worth finding another bug database app, or even be crazy and write our own for a long term solution. Cheers- Here's the question, gnome's bugzilla has over twice as many bugs as we have, is quite speedy and doesn't seem to suffer from the OOM killers that our bugzilla has. So what's the difference? Did gnome just toss hardware at the problem to make it go away or have they done something to make bugzilla work for them? I think throwing hardware at the problem is the wrong approach in this case, as its just delaying the problem that has made the new hardware seem like the solution...which will no doubt creep up again. Don't get me wrong, the donation of hardware from gni is greatly appreciated. I'd just to see that we try and see why we have the problem in the first place as well. As I'm sure that this problem will creep up again -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE021uSENan+PfizARAifIAKCQ1g0sVRxvAbpm1khTCLfw9KxOTgCcD1lo 6Arc6MGKDoqRTfZWgvWR1fQ= =5gzO -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Make FEATURES=test the default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin F. Quinn wrote: I'd like to suggest we make FEATURES=test (and therefore USE=test) the default behaviour, rather than the opt-in we currently have. Far too many packages fail their test phase. Since we encourage users to set CFLAGS in ways that upstream may not have predicted, if upstream go to the trouble of providing tests it seems sensible to me that they should be run, unless there is a very good reason not to run them. This will help pick up faults that are due to the compiler version, CFLAGS etc much more consistently. At the very least, ebuild maintainers and ATs should be running with tests switched on. If the tests are known to fail then the ebuild can either RESTRICT=test, or just return successfully from src_test() where the test report is useful even if some tests fail. Thoughts? I can say from experience that there are a great heaping load of packages currently that fail their test suite, the sci-team seems to be the best in this regard for passing the tests successfully. If we do in fact plan on making this the default, we should be prepared for a increase in bugs from users who will now have ebuilds stop on failed test suites. While I agree that it would be nice to see more people using test and collision-protect I don't think its something we should enable at this point in time till we have many packages working correctly with the feature. If however people feel that by enabling it, that it'll make us actually fix these issues then I'd like to see it move forward. I'm just curious as to why this has come up suddenly Kevin? p.s I hope all dev's run with test and collision-protect, I know I know you don't but I can hope. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE0+VtSENan+PfizARAhNtAKCclIg8ikGcaTgQ9E5YPBjPj93IlACeJyNX ER9yFoXQ3hOKzoMq4OxL3Rg= =uS4D -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Project Sunrise resumed again (was Resignation)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ciaran McCreesh wrote: Knowing what the problem is is part of making the solution. The problem is not that users can't push arbitrary content into a centralised official repository with no oversight from the herds appropriate for said content quickly enough. I didn't claim to know exactly what the real problem is, merely that it's not what's being solved here. There is a lot of irony in this entire discussion. We are actually talking about going against what the heck part of the reason this project was started. Are we seriously that *can't find the word I'm looking for* idiotically to not see that we're arguing over not allowing a user a choice in what they want to do. That we are so high and mighty that we automatically know what is better for the user then they themselves know? Who defined us as the ones to make that choice for someone else, when we are supposedly about allowing choice. That is the issue at hand at the core of this. Its called choice. People can choose to use a separate program to download the sunrise overlays. That separates it entirely from the core tree itself. A disclaimer for checking out could be added that is prominent that will warn that these are a service provided to the community from the community. That those who have gone through the developer mentorship will continue to work on the core of the heart of gentoo, allowing us to focus and make the product so much better and quicker that you'll be blindsided with the new improved product. We'll have a rebirth so to speak. Bloody, I mean seriously...think about what it is we are arguing over, and then remember what gentoo is, why you came to it in the first place. That will probably tell you where it should go. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEza2pSENan+PfizARAtG2AJ9vvGWRcsRfNtr8oUGgRnK79dcADwCfdP1I qiTETbjrFc2qBrLYFiHn3xM= =Oofv -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Nominations open for the Gentoo Council 2007
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thierry Carrez wrote: Those were nominated but did not (yet) confirm their participation : tsunam While honored to be possible considered to be able to help guide the technical direction of gentoo. I however don't feel that I'm capable of it at this time. Too many other things are taking my time within the project. It'd be fun to see how low I'd be on the voting scale but as if I was to somehow miraculously far enough up on the list to be elected, I'd not be able to accept that position. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFEzSfSSENan+PfizARAq/gAJjmAmnAsg+6v1VKdBSK5k25rdPrAJ4mbA22 0+2Fm13PtPWX8rUNc/1OTA== =QGO5 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Resignation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ciaran McCreesh wrote: On Sun, 30 Jul 2006 23:20:16 -0500 Alex Tarkovsky [EMAIL PROTECTED] wrote: | This no QA accusation is a complete myth. QA led by actual Gentoo | developers is indeed in place at Sunrise [1]. Did you look at *which* actual Gentoo developers are on the list? Even that aside, if a couple of hundred developers can't handle doing QA for all those maintainer-wanted ebuilds, what makes you think four people can? Really now Ciaran, if you have issues with those people. Take it up with them. You've yet to state a reason why it concerns you. Its no better then the people who are saying that it'll be a huge QA issue but they are not elaborating on it. As some are aware and some are not, the basic job I do for gentoo is a QA one. I help to ensure the x86 arch tree is hopefully as stable as possible. So if anything this will affect me directly. I however want to see what the project can do. If it does end up as a problem then it can be killed off, but doing so before it has a chance to fly is part of what has been keeping us from innovating as a distribution. It means we're maturing, but we are still a community project and as such should be allowed to fly with possibly wild idea's when it suits us. As well, we are all human, as you are Ciaran. This means that we make mistakes. However, what you are also asking is to NOT trust those people who are qualified to be part of gentoo to be able to do the work and perform it in a decent way. I will not begin to doubt any of the people who have the gentoo flag as part of who they are because of being human. As has been said as well, we learn more from the mistakes we make then somehow having avoided it without realizing why. Thirdly, I know one of the issues with one of the leaders of the project, is the fact that they are not a ebuild developer. I'd like to have them take the second quiz simply to prove that they have the knowledge to be trusted to review the ebuilds. Course with the number that he's seen I'm sure he's helped take care of things that would make the rest of us go...how did they think that was ever a good idea. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEzY0sSENan+PfizARAu2kAJ488MHWDCtFY8SKetoC1wxFtpPk7wCfW97W DxJvWeVcd87OukymD/M+Crs= =kdC9 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Funding from Gentoo UK 2006 event
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wernfried Haas wrote: On Tue, Jul 25, 2006 at 05:34:31PM +0100, Stuart Herbert wrote: Dunno about other folks, but I'd be very happy to see us return to the Resource Centre once more. I thought that it worked well as a venue, and that London is the right place to hold the conference. Resource Centre was fine, maybe i'll manage to stop by next year too. I think the good financial outcome is George's fault, he forced me to donate 3 pounds. Someone make sure it goes into $MY_PROJECT ;-) cheers, Wernfried % $MY_PROJECT hmm, that returned nothing *hides the cash in my pocket* guess you didn't define the project, and your loss is my gain ;) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFExk8RSENan+PfizARAseOAKCKInf8KdbU7T+xYxkWtnbh4Rd/MgCfbUYb i1KgC7tkYmMvtP4+hsPzxNg= =Vq7R -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Linux World Expo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 less. We don't have enough dev's close enough to san fran to allow a whole bunch of us a floor to crash on as far as I know. If however you are, give us a shout with floor space ;) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEsp6zSENan+PfizARAubpAJ9/NtTBUuB2XRkfz0kb6vHoD5zDKgCfRVah WHNtV25i/a5VJnvc80EpmZc= =fUaW -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: [gentoo-core] IMPORTANT: bugs performance issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thank you to all of our sponsors and especially GNI for being so gracious and giving to us. Not even a little tiny bit of compiling? A smidge? pretty please with a cherry on top? Yay, *plop* !!! (And no, tsunam - no compiling there :P) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFErUohSENan+PfizARAtGqAJ9du+4mdXYqEyjTmn5u4cwMyfWHVQCffhhn LSd4QYOi4AeiJWkYPgDgA5I= =W5ou -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Replacing cpu-feature USE flags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Or instead of throwing a hissy fit yourself about diego not agreeing with you..I don't know you could go and show the way that you feel it should be done and show the technical merit. Ciaran I will give you that you are a capable programmer, and had valid arguments in this thread. However, when interacting with people and proving points on merits you seem to go out of your way to not prove anything and throw examples out there without really backing them up. No, Diego. The argument is that you're coming up with a horrible and unnecessary hack where there are far cleaner alternatives, and that you're blindly sticking to it and trying to throw off any objections by devious means because you don't want to scrap said hack after all the misguided effort you've spent on it. However, since you seem to be incapable of admitting the gaping flaws in your own work, I'm asking for someone else to point this out to you in a formal manner rather than watch this thread go on for even longer. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFErYFLSENan+PfizARAjzzAJwIue9UDtwsANxaaqqnVJVr0jTz6ACglAL6 cO7O0Pw+CGDfFlVdY7z1N3o= =6G6V -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] bugzilla 2.22 masked ~x86
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Weigelt wrote: Hi folks, I've just seen, current bugzilla is masked, and DBD::Pg too. As the documentation states ~x86 means, it's working, but not properly tested on this platform (ie. x86). How does the process of proving packages work ? I've made good experiences with bugzilla-2.22 - the whole installation (including the webapp installer) worked good. The only things I had to do by hand were adding the vhost to apache and creating the user and database in postgres, but mayb that's meant to be this way. cu Please file it with the maintainer/herd of the package, instead of directly to the arch team you want it stable. In this case x86. It makes it easier for the arch team to not have to filter through bugs and track down maintainers ourselves. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEq98QSENan+PfizARAuOmAJsGHDubaNIN3gQmIMJ8wz2/Dny3CACfcgv1 gsWKO8FNr0r2Z5ZFYW5/n3w= =96km -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Mobile Computing herd severely understaffed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 x86 AT O_o *bonks nightmorph on the head* you're a developer! that's almost, well entirely, a step in the opposite direction. We could use the help on the x86 team as well. And we're not overbearing, only needing you to test 4 packages in a month with three warnings of inactivity before getting the boot. You know you love us as well ^.^ I'm on devaway for a month, but when I'm back, ping me and I'll see if I can help out in any way. Since I really need to help out with x86 AT anyway, I might as well double up and do laptop-related stuff if possible. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEq+CqSENan+PfizARAm66AJwPBoCn4T1Bw/RQJiMjqtF6er+xbQCffWYM GzrJQ1V8Yf/znruv4F0dXz4= =KRw0 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Re: Re: GPL and Source code providing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jakub Moc wrote: Curtis Napier wrote: If it's decided to go with this idea I think we should mark it up a little, even if it's only a dollar or two. People actually don't mind paying a little if it's going to go towards helping Gentoo. We get tons of threads asking about donating in the forums so this would be a good way to help with that (even if the DVD isn't purchased very often). --Curtis You can't do that according to GPL-2, see esp. the part: 3. b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution , a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, manpower cost? *nudge* however it'd be good to keep it low low low.. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEq/fbSENan+PfizARAtFuAJ9GjWOU/kZ4QsgFkx//RGIuctfo3ACfXY9v rU2VwLX8uRQyc+hWN0i8N28= =Zwc2 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Nominations open for the Gentoo Council 2007
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Frysinger wrote: On Tuesday 04 July 2006 16:39, Kevin F. Quinn wrote: On Sat, 1 Jul 2006 02:46:59 -0400 Mike Frysinger [EMAIL PROTECTED] wrote: well it's about that time of the year ... time for nominating people for the next Gentoo Council I nominate SpanKY, vapier and Mike Frysinger. thanks, one of us accepts -mike does that mean that only one third of your personalities will be productive in meetings and the other two disruptive? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFErE0HSENan+PfizARAlQ+AJY5VRs6idw8Uzn8hq2xo+IM/awvAJ9fc/t4 btSDNdF+8ttr5oJltYhJ/A== =hPPh -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Future developer
Paul de Vrieze wrote: I'm proud to announce the arival of a future developer. His name is Tom. He arived last monday on 10:22 am (UTC+02). I and my wife will take care of mentoring him to full developership ;-). In the meantime, he's got his own album on http://www.cs.ru.nl/~pauldv/tom/ Paul ps. If I'm a bit away these days, it is due to me being preoccupied with my mentoring task. Does this make him the youngest mentee that we've had. I think we need to make a announcement about that on the front page. Congratulations on bringing a little one into the world. Look forward to many many sleepless nights. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Assigning bugs to treecleaners
As long as it doesn't involve spanky I think we won't lose all our users because they suddenly became blind. Its the first time I've heard of the project as well. I knew that there were a few people going through and removing stuff but... (that's right, i'm recommending the special centerfold issue of the gwn a few times a year ;) -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Resignation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Another one bites the dust Another one bites the dust And another one gone, and another one gone Another one bites the dust Hey, Im gonna get you too Another one bites the dust -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEngJPSENan+PfizARAtd+AJsExp/AioX1rRHKa2Gxxo+NvMmnhACfee/H v7s1dc4z8voTjxfMW/FivRI= =sv3j -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] [Last Rites: app-admin/scotty]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What no! not scotty. Who's going to beam us all up now and repair the ship in half the time that he says it'll take! Alec Warner wrote: Scotty has been pmasked due to sandbox violations[1]. I spent about 30 minutes looking at them and solving them is not as simple as I'd first hoped, I asked trelane to double check my logic and he came to a similar conclusion. As such with no maintainer or herd this package is scheduled for removal in 30 days and has been pmasked. If you have any questions please contact the treecleaner[2] project or comment on the bug[1] Thanks, Alec [1] http://bugs.gentoo.org/show_bug.cgi?id=77501 [2] [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEmhZ9SENan+PfizARAj6RAJ9RvcK5h7IoKWEDSrEtSr9qKqRE5gCeM02j MQ+D+yzpZ7fxGcVNHmqeN/I= =CLfi -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] using specific gcc-version in ebuild
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Forcing a change in your gcc version for compiling is less then optimal. I don't believe the eclass has anything in it that will help in what you are trying to do. I would probably do a pkg_setup with a check for the version of gcc if it isn't a 3.* version then you exit building and give the reason for this...This would probably be the best way to do it, at this point. [EMAIL PROTECTED] wrote: What about gcc-config - will that work? From: Sven Köhler [EMAIL PROTECTED] Date: 2006/06/16 Fri PM 03:10:08 EDT To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] using specific gcc-version in ebuild -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEkwcUSENan+PfizARAjLdAJ9u6zhasuWe4AT5x3+rcOAMlgqovwCeLPNf NLU57K0Bl7uuneLhujKRLck= =nSTb -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] User Relations Co-lead
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Of course it will! \^.^/ You can't go wrong with the anime smily faces _. Thanks for the luck, I know I'll need it Andrej Kacian wrote: Will that result in dramatic increase of anime smilies in Gentoo environment? ^_^ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEge8nSENan+PfizARAk+hAJ92wZvimaJkzzVpigSUhGq0eHxP9ACfcpzA 522ChEUc/GSw6OcDFrAtxkg= =A5Ur -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] app-cdr/dvdrtools needs a newer version stable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've not been able to move my dvd burner from my server over to my development box yet so I have not been able to look at it yet. (the joys of moving hardware between machines :-P when both need it. Well hopefully not much longer as I'll be replacing the server after this new jobs paycheck. Anyways as stated in the below bug there is a issue for some with this and I haven't had the oppertunity to see if I can replicate it and get a proper backtrace to metalgod. I'll try to get to that as soon as I possibly can, hopefully this weekend as the request has been with us for a while. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFESDQ+SENan+PfizARApSpAJ99w6bmuTAveRmEmyJhRECEpdqUrQCgmZTs WuoioLXuGh3RXk5FFZENJLY= =nZgM -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] New Dev: antarus (Alec Warner)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Harring wrote: Hola all- We've got a new portage dev; Alec Warner, aka antarus- aside from doc work, he'll be doing repoman work and the usual random bug squashing. Welcome antarus, might I also mention that he helps out the x86 team as well. Glad to have you aboard -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD5bmPSENan+PfizARAkVKAJ4rKK88uGyntqTObyKmBMua0Ki9DQCdE8Cp c7+OJwAJ9+19Ba+CN8YjIQ8= =TDKf -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Unmasking modular X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Donnie Berkholz wrote: Joshua Jackson wrote: In the oldest version of the package (as all these were), I don't see much point in the change. They will be removed within a fairly short amount of time. Fairly short meaning what, 6 months? A lot of old ebuilds tend to stick around forever. True, some older packages stay around longer then they probably should, and was a exageration on my part but it does prove the point that the check is somewhat superfluous for most users, since it seems that most people (from a rough estimate of 2 years on the forums) seems that 1month is about the outside for most people's updates. As the point has been brought up about packages being in there longer, it'd be interesting to write something to do a check for multiple stable versions with a older version being =6 months old. Something I might go look into. Secondary, you are suggesting that any dev who comes across a modular x problem to fix it..even if this is a direct violation of the guidelines set forth in the documentation? Which guidelines, exactly? I'm having trouble finding these vague guidelines to which you refer. I found one that said If you make an internal, stylistic change to the ebuild that does not change any of the installed files, then there is no need to bump the revision number. I also found When a package version has proved stable for sufficient time and the Gentoo maintainer of the package is confident that the upgrade will not break a regular Gentoo user's machine, then it can be moved from ~ARCH to ARCH, which, to my reading, can also apply to transferring ~arch modular X deps to stable. Thanks, Donnie To quote one of the ebuild-quiz questions: You wish to make a change to an ebuild, but you checked the ChangeLogs and metadata.xml and it appears to be maintained by someone else. How should you proceed? A general response that is obtained from the documentation source (either the unofficial dev guide or the developer doc's) Concerns getting in contact with the maintainer before you make the changes. Explaining the how and why and either asking them to take care of it or asking for permission to do so. We've had many developers get highly upset at another developer changing even a minor thing in their ebuild...such as the simple changing of depends. Bringing it back around to Mark's initial point, the check causes extra work for a arch developer that would require stepping on another herd/developers package's..this is a Relations nightmare. Not to mention Quality Control implications it can have, something that I think as a whole development community we've worked very hard at improving vastly. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD3x1lSENan+PfizARAqFoAJ9tAQ9UI0X3MCXG9A7DjWgrheBWfgCgnUG+ gRDzL4aW8JKoiZEcdNAPgLk= =/VRh -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Unmasking modular X
Mark Loeser halcy0n at gentoo.org writes: Donnie Berkholz spyderous at gentoo.org said: Jason Stubbs wrote: The patch now has the debugging output and x11-base/xorg-x11 check removed. Excellent. Works perfectly. Since we're failing on them, perhaps we can say obsolete instead of deprecated? 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, I will have to agree that this change has made it a pain to mark anything stable. I had 4 out of the 6 I did today bail out because of this. I took the simple easy fix and removed the check to stabalize the packages I needed to. I know we have people who want modular X yesterday, but causing trouble for dev's going about business that doesn't involve the modular problems directly is only going to cause resentment and frustration to all the teams involved. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Unmasking modular X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Donnie Berkholz wrote: Joshua Jackson wrote: I will have to agree that this change has made it a pain to mark anything stable. I had 4 out of the 6 I did today bail out because of this. I took the simple easy fix and removed the check to stabalize the packages I needed to. I know we have people who want modular X yesterday, but causing trouble for dev's going about business that doesn't involve the modular problems directly is only going to cause resentment and frustration to all the teams involved. Why is the simple fix not copying over the already fixed dependencies in the latest ebuild? It's not as if that's a lot of work. That's the intent of this failure -- to avoid flyby commits by people when they could just fix the deps (which are already available in ~arch) while they're there. Thanks, Donnie In the oldest version of the package (as all these were), I don't see much point in the change. They will be removed within a fairly short amount of time. Secondary, you are suggesting that any dev who comes across a modular x problem to fix it..even if this is a direct violation of the guidelines set forth in the documentation? I'm curious as to why you want potentially 200+ dev's to violate it, to push modular so quickly? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD3wfrSENan+PfizARApkUAJ4/Rfr/iMwZMD1lCkhwBnGH+BhUVwCdHqsD Rc97k6+FBAKp59MAa2t16Ig= =P92T -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: x86 arch team leads
Mark Loeser halcy0n at gentoo.org writes: Well, the x86 team has now chosen some leads so we can start getting everything together as a team. For our leads, we have chosen to have a committee of 4 of us: halcy0n, solar, azarah, and wolf32o2. We each felt that we didn't have the time or experience to be able to handle being a sole lead by ourselves. Just letting everyone know what is going on with the team. Mark All hail our new x86 overlords ;). Congrats to the four of you on taking up the responsibility to deal with all of us that will be part of quite a large team. Looking forward to how things move forward. -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Resolution - GTK Useflag Situation
A few more that I didn't see in the list media-libs/imlib : gtk1 only media-libs/smpeg : gtk1 only media-sound/lame : gtk1 only media-video/mplayer: gtk1 it would appear? -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: cdparanoia and libcdio
I have to agree with Flameeyes(diego) on this one. If the switch needs to be made, no matter what is done. There will be one package that will slip through and need to be patched. Would be better to get them as we know about them/have users reporting them. I can think of one or two that should be fairly easy to patch right now. I'll take a look at them to see if i can manage to figure out the code enough to supply the patch upstream. Course in the mean time we'll have to apply it outselves. I think this relies a lot on what the media-herd feels. It'll add a lot to their plate. If they feel they can handle it then I don't see why we can't start to make the change over. Just do it in stages. -- gentoo-dev@gentoo.org mailing list
