Re: [gentoo-dev] Gentoostats, SoC 2011
i am a user and i am ok with opt-out if the std data that is transferd is compleatly anonymized so no sensitive data. and if the user wants to register his/her machine pkg's more data is trasnfered thx Mario 2011/8/24 Thomas Kahle : > On 13:03 Wed 24 Aug 2011, Andreas K. Huettel wrote: >> Am Mittwoch 24 August 2011, 12:48:35 schrieb Patrick Lauer: >> > >> > If you sneakily add something to cron.daily by default you can get >> > pretty nice coverage. But I guess anyone trying that in Gentooland will >> > meet some rather unpleasant resistance :) >> > >> >> Of course, we could place it in some blatantly obvious way into a default >> configuration, together with a big fat message what it does and how to >> quickly disable it. >> >> We'd get better coverage in an opt-out system than in an opt-in system. >> >> (First idea- package is pulled in by a default-on useflag and installs >> itself into cron.daily. BEFORE it runs the first time it outputs said >> message and asks for permission to proceed (which cannot be done in the cron >> job obviously but we'd find a way).) > > Sorry, but NO. If you want you can make a big noise message that asks > users to install the cron-job but opt-out is not an option here. > > > > -- > Thomas Kahle > http://dev.gentoo.org/~tomka/ >
Re: [gentoo-dev] package graveyard
most users just hunt the program name and gentoo to a searchengine they get the info that the ebuild is in cvs but in graveyard. but hey i am just a user. Mario 2011/8/17 Markos Chandras : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 17/08/2011 06:04 ??, Mario Fetka wrote: >> how about adding a new tag metadata,xml so that it is not imported >> into the rsync tree >> > What is the difference between your proposal and removing the package? > In both cases, the broken ebuild does not get propagated to users. > > - -- > Regards, > Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.18 (GNU/Linux) > > iQIcBAEBCgAGBQJOS/bcAAoJEPqDWhW0r/LCKGEP/AnDf0J9DVaRKfS6vpciexHx > QY8HEKnwQs5wUHnjxWvwl4135NwA5mZ2jJw6upgddDjbZaBh9a5L9yZOIS5VE9k1 > 2vCu+rTBdugqp5oHpFDtNpdW0QwMI1vcUJCUQR51jtZNqR/0CrBtaWtAvL4lhN+1 > cyYsTQyRR5zyaA19WZlzXYZybv6m9N7tZYxEXf/usFBy/T8x21aH2igt5OFld1ts > XVxV25QKhC2D2sNMbHJ/YJvyd8f/AQBidekCOR8PcgbJPTiS8HDvGgMO9QP2CFX3 > ksFsEFSA9W8HXdDtaYY2SN7bbAYyCK0zP2x6e693ndAiCvwM3UqRWkBR9DCIfkYm > o5h9uY7kgCbH0wQc/5/fpf8buPS3UHIcmlopQoqMn9qhIEL36O/QN5JX4NEFt9JQ > s4sJf/zS6lLbDv2hZB/Efdo2L33CCIlF28BukL+WyfR2OBtDdIQdxvQmhLXkFTkv > v8AYufyTtKZ4NRMzFXlXdJ3t0PdUNyX7P5+g2V5VBPaz3TtsFC8u9K1byK5ApTH8 > 9PBBHTs4NjriMS1JQFQWIZIG1TpxcSJAk6Xda+O64RSUfs7ajfGK7JyiPNAJPSWr > EIEtv7Rc40pDjjbAybRkN7onbOq107XTA+rWsXCMI4oOMcNZBzv81OUVk6L3qt9h > dsBPgWmweXQ+DktfDo8P > =vwO5 > -END PGP SIGNATURE- > >
Re: [gentoo-dev] package graveyard
how about adding a new tag metadata,xml so that it is not imported into the rsync tree Mario 2011/8/17 Alex Alexander : > On Wed, Aug 17, 2011 at 19:45, Thomas Kahle wrote: >> Hi, >> >> I'm forking from a thread on gentoo-project: >> >> On 17:26 Wed 17 Aug 2011, Markos Chandras wrote: >>> Personally, I want to shrink portage. There is no way for 250 listed >>> developers ( I would be glad if 100 of us were really active ) to >>> maintain thousands of ebuilds. >> [...] >>> We need to support only the packages that we can *really* support and >>> lets hope that more people will join in when they see their packages >>> going away. >> >> I like the idea of shrinking portage, but here's a scenario I'd like to >> avoid: >> >> 1) package A is unmainted, but has a sophistacted ebuild that evolved >> over some time. >> >> 2) A has an open bug that nobody cares to fix, treecleaners come around >> and remove A. >> >> 3) New dev X joines Gentoo and cares for A and startes to rewrite the >> ebuild from scratch. >> >> Is there a way for X to easily query the portage history and dig up the >> ebuild that was there at some point. She could then use the old ebuild >> for their new version, but without efficient search she would probably >> start from scratch. Some packages are treecleaned in the state 'working >> but with a single bug (and nobody cares)', it would be good if that >> state is somehow retained after the removal. Then you can get a fully >> working package while fixing only one bug. >> >> Searching through mailing list archives with automatted removal mails >> would be my hack, what would be yours? >> >> Cheers, >> Thomas > > We could try removing all keywords and masking ebuilds that are > abandoned with bugs but upstream is still active, instead of removing > them completely. That way the ebuild will be there when/if someone > else decides to take care of the package and it will even show in > tools like eix. > > -- > Alex Alexander | wired > + Gentoo Linux Developer > ++ www.linuxized.com > >
Re: [gentoo-dev] Last rites for net-dns/ldapdns
Am Samstag 26 Dezember 2009 06:47:51 schrieb Victor Ostorga: > On Fri, 25 Dec 2009 07:00:22 -0800 > > Joshua Saddler wrote: > > On Wed, 23 Dec 2009 10:40:06 -0600 > > > > Victor Ostorga wrote: > > > # Víctor Ostorga (23 Dec 2009) > > > # Last bump in 2005, does not build against current > > > # stable net-nds/openldap-2.4.19-r1 bug #247956 > > > # Removal in 30 days > > > net-dns/ldapdns > > > > So what about http://www.gentoo.org/doc/en/ldapdns-guide.xml -- you > > want the GDP to just remove the doc? We can do that. > > Yes, it will be needed to remove the doc. > > > Is there a compatible drop-in replacement that will allow us to > > s/ldapdns/foo throughout the guide? > > Unfortunately, I don't know an exact replacemente for ldapdns, at some > point I heard about a LDAP sdb back-end for BIND 9 [1], but don't know > if it is still functional. > > [1] http://bind9-ldap.bayour.com/ > and also powerdns has ldap support the bind sdb ldap backand is in tree both ldap backands share the same ldap structure with some small diffferences Mario
Re: [gentoo-dev] Retiring
On Monday, 4. May 2009 19:06:12 George Prowse wrote: > Peter Faraday Weller wrote: > > Hi > > > > Thanks, > > welp > > Sad to hear it mate. > > As the person who did your first install for you (i think) I think you > will be missed. > > I am quite surprised about what you said about the state of things > because i've got the distinct impression from others that Gentoo has > been improving in the past 12 months. > > About the lack of the developers, something I proposed about 3 years ago > might be applicable: has Gentoo ever thought about doing a "Dev Day" in > much the same way as the "Bug Days"? Advertise a day where people can > come and have a chat with developers and get coached because there is a > vast amount of people and knowledge out there and I never see anything > about Gentoo wanting people. > > If you book them, they will come. > > G and I would be the first to come Mario
Re: [gentoo-dev] Retiring
On Monday, 4. May 2009 19:06:12 George Prowse wrote: > Peter Faraday Weller wrote: > > Hi > > > > Thanks, > > welp > > Sad to hear it mate. > > As the person who did your first install for you (i think) I think you > will be missed. > > I am quite surprised about what you said about the state of things > because i've got the distinct impression from others that Gentoo has > been improving in the past 12 months. > > About the lack of the developers, something I proposed about 3 years ago > might be applicable: has Gentoo ever thought about doing a "Dev Day" in > much the same way as the "Bug Days"? Advertise a day where people can > come and have a chat with developers and get coached because there is a > vast amount of people and knowledge out there and I never see anything > about Gentoo wanting people. > > If you book them, they will come. > > G and I would be the first to come Mario
Re: [gentoo-dev] The Plethora of Patches
Am Donnerstag, 14. August 2008 17:24:41 schrieb Santiago M. Mola: > On Thu, Aug 14, 2008 at 4:17 AM, Andrew D Kirch <[EMAIL PROTECTED]> wrote: > > Patches in the metadata.xml should have some sort of status tracking for > > each patch, repoman should flag any that don't, and warn on any that have > > not been submitted upstream unless the status is signed off on by a herd > > leader (such as Gentoo specific patches). This would provide visual > > feedback for users and developers with regard to a pretty important > > metric on how successful Gentoo is at getting patches pushed back to > > developers. > > It was proposed recently to add some standarized headers to all new > patches for maintenance purposes. Something like: > > Source: patch by John Foo, backported from upstream, whatever. > Upstream: In revision 245, rejected, foo. > Reason: Build system sucks > > I think that's all we need in order to know how were things when the > patch was added and if it needs to be pushed/tracked upstream, removed > in the next version of the package, etc. > > Some of us already put these kind of headers, or at least an URL to > upstream bug or a meaningful source of info about the patch. > > However, tracking the status of every patch since its inclusion in > portage until it's removed would be a huge work overhead... and I > doubt it's worthy. i am using the lfs tool to create my patches: http://www.linuxfromscratch.org/patches/downloads/MAINTAINER/lfspatch it creates patches with patch version number: irtrans-irserver-5.11.08-arm_remotes-1.patch and the header it creates looks like this: Submitted By: Mario Fetka (mario-fetka at gmx dot at) Date: 2008-07-18 Initial Package Version: 5.11.08 Origin: me Upstream Status: unknown Description: add back remotes and correct makefile arm dir location i think some rules for patches would be a good thing. i would also suggest naming rules for the patches Mario
Re: [gentoo-dev] Re: Removing .la files...
Am Donnerstag, 19. Juni 2008 16:22:19 schrieb Olivier Crête: > On Thu, 2008-06-19 at 14:08 +0200, Rémi Cardona wrote: > > > Why only plugins? What's to stop an application from loading a > > > "normal" library using libtool's dlopen wrapper (perhaps so it can fail > > > gracefully if the library is missing, for example)? > > > > Nothing per se, but I have yet to see any FOSS application dlopen() gtk+ > > or libpng. > > FOSS is the keyword here... the flash plugin dlopens a bunch of stuff also kde-3.5 is using libtools dlopen for plugins signature.asc Description: This is a digitally signed message part.
[gentoo-dev] Webapp with plugins
Hallo list, I stumble across a nice problem: At the moment i am creating the ebuilds for the Mandriva Management Console (http://mds.mandriva.org). the web Interface is php based so the webapp eclass would be the best way but know the show stopper the webiterface supports plugins so how can i say that this webapp is a plugin for another webapp thx in av Mario (geos_one) p.s.: if i have directed the request to the wrong list plz direct me to the right one thx. signature.asc Description: This is a digitally signed message part.
