If one tries to modify the ebuild and test a change, the system issues a file size error. How do you get around that?
--- On Mon, 3/29/10, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: > From: Paul Hartman <paul.hartman+gen...@gmail.com> > Subject: Re: [gentoo-user] Re: help > To: gentoo-user@lists.gentoo.org > Date: Monday, March 29, 2010, 11:11 AM > On Mon, Mar 29, 2010 at 10:11 AM, > Stroller > <strol...@stellar.eclipse.co.uk> > wrote: > > > > On 29 Mar 2010, at 13:22, Dale wrote: > >>> > >>> ... > >>> Filling bug reports is important. I filled > over 50 on b.g.o this year > >>> alone. All of them are version bumps or bad > homepages. Some programs haven't > >>> been bumped for 5 years. > >> > >> That is true but I don't have a account > there. Someone else does so they > >> filed it for me. I don't guess it matters > who files it as long as it is > >> filed. > > > > It's helpful if you can subscribe to email updates, > and help test when > > revisions are available. > > > > Sometimes an ebuild is posted to as an attachment to > the bug - you download > > it and add it to your local overlay. Thus you may get > the updated version > > before it's available in the Portage tree (some > ebuilds are attached to bugs > > for packages which never become accepted) and you can > at least add a "works > > for me" comment and encourage the devs by remarking > how useful it is to you. > > And even if you've got nothing new to contribute to the > problem, you > can vote for bugs that are important to you. > >
