| 1 |
On Fri, Jan 30, 2004 at 09:38:25PM +0100, in <401AC0C1.6010701@×××.li>, |
| 2 |
Jan Schubert <Jan.Schubert@×××.li> wrote: |
| 3 |
> Jon Portnoy wrote: |
| 4 |
> >On Fri, Jan 30, 2004 at 09:21:57AM -0800, Drake Wyrm wrote: |
| 5 |
> >>On Fri, Jan 30, 2004 at 11:56:21AM -0500, in |
| 6 |
> >><20040130165621.GA12724@××××××××××××××××××.us>, Jon Portnoy |
| 7 |
> >><avenj@g.o> wrote: |
| 8 |
> >>>When working with ebuilds, please keep in mind that RDEPEND should |
| 9 |
> >>>contain everything that needs to merge when installing from a tbz2 |
| 10 |
> >>>binary package, but that's all -- anything else is cruft. DEPEND should |
| 11 |
> >>>contain everything needed to build and install the package. |
| 12 |
> >>I've had a question about that; this seems a good time to ask. Should |
| 13 |
> >>DEPEND include the run-time DEPs or *only* compile-time DEPs? |
| 14 |
> >Only compile-time deps. |
| 15 |
> So, where should i put runtime deps when installing from source? If i |
| 16 |
> understood you right, neither RDEPEND nor DEPEND is the right place? |
| 17 |
|
| 18 |
Runtime DEPs will be the same (for similarly-configured packages) |
| 19 |
whether you install from source or from a binary package. Jon was (if |
| 20 |
I understand correctly, your milage may vary, batteries not included, |
| 21 |
void in the state of New Hampshire) not *defining* RDEPEND, but offering |
| 22 |
a litmus test to help answer the question, "Does this belong in RDEPEND?" |
| 23 |
|
| 24 |
-- |
| 25 |
Batou: Hey, Major... You ever hear of "human rights"? |
| 26 |
Kusanagi: I understand the concept, but I've never seen it in action. |
| 27 |
--Ghost in the Shell |
Archives