| 1 |
On Tuesday 30 March 2010 01:57:05 dan blum wrote: |
| 2 |
> If one tries to modify the ebuild and test a change, the system issues a |
| 3 |
> file size error. How do you get around that? |
| 4 |
|
| 5 |
|
| 6 |
ebuild /path/to/ebuild/file.ebuild manifest |
| 7 |
|
| 8 |
explanation: man ebuild |
| 9 |
|
| 10 |
However, your next --sync will revert your change. Copy the ebuild to your |
| 11 |
private overlay and modify it there to preserve your changes. |
| 12 |
|
| 13 |
More details: portage documentation gotten via: |
| 14 |
|
| 15 |
equery files portage | grep man |
| 16 |
|
| 17 |
|
| 18 |
|
| 19 |
|
| 20 |
|
| 21 |
|
| 22 |
> |
| 23 |
> --- On Mon, 3/29/10, Paul Hartman <paul.hartman+gentoo@×××××.com> wrote: |
| 24 |
> > From: Paul Hartman <paul.hartman+gentoo@×××××.com> |
| 25 |
> > Subject: Re: [gentoo-user] Re: help |
| 26 |
> > To: gentoo-user@l.g.o |
| 27 |
> > Date: Monday, March 29, 2010, 11:11 AM |
| 28 |
> > On Mon, Mar 29, 2010 at 10:11 AM, |
| 29 |
> > Stroller |
| 30 |
> > <stroller@××××××××××××××××××.uk> |
| 31 |
> > |
| 32 |
> > wrote: |
| 33 |
> > > On 29 Mar 2010, at 13:22, Dale wrote: |
| 34 |
> > >>> ... |
| 35 |
> > >>> Filling bug reports is important. I filled |
| 36 |
> > |
| 37 |
> > over 50 on b.g.o this year |
| 38 |
> > |
| 39 |
> > >>> alone. All of them are version bumps or bad |
| 40 |
> > |
| 41 |
> > homepages. Some programs haven't |
| 42 |
> > |
| 43 |
> > >>> been bumped for 5 years. |
| 44 |
> > >> |
| 45 |
> > >> That is true but I don't have a account |
| 46 |
> > |
| 47 |
> > there. Someone else does so they |
| 48 |
> > |
| 49 |
> > >> filed it for me. I don't guess it matters |
| 50 |
> > |
| 51 |
> > who files it as long as it is |
| 52 |
> > |
| 53 |
> > >> filed. |
| 54 |
> > > |
| 55 |
> > > It's helpful if you can subscribe to email updates, |
| 56 |
> > |
| 57 |
> > and help test when |
| 58 |
> > |
| 59 |
> > > revisions are available. |
| 60 |
> > > |
| 61 |
> > > Sometimes an ebuild is posted to as an attachment to |
| 62 |
> > |
| 63 |
> > the bug - you download |
| 64 |
> > |
| 65 |
> > > it and add it to your local overlay. Thus you may get |
| 66 |
> > |
| 67 |
> > the updated version |
| 68 |
> > |
| 69 |
> > > before it's available in the Portage tree (some |
| 70 |
> > |
| 71 |
> > ebuilds are attached to bugs |
| 72 |
> > |
| 73 |
> > > for packages which never become accepted) and you can |
| 74 |
> > |
| 75 |
> > at least add a "works |
| 76 |
> > |
| 77 |
> > > for me" comment and encourage the devs by remarking |
| 78 |
> > |
| 79 |
> > how useful it is to you. |
| 80 |
> > |
| 81 |
> > And even if you've got nothing new to contribute to the |
| 82 |
> > problem, you |
| 83 |
> > can vote for bugs that are important to you. |
| 84 |
|
| 85 |
-- |
| 86 |
alan dot mckinnon at gmail dot com |
Archives