On Mon, Jul 24, 2000 at 04:23:22PM -0400, Matt Zimmerman wrote:
> On Mon, Jul 24, 2000 at 03:17:55PM +0200, Adrian Bunk wrote:
>
> > I'm looking for an easy way of getting the build dependencies of a
> > package. At the moment I do look through the build log manually, and if I
> > oversee somethi
On Mon, Jul 24, 2000 at 03:17:55PM +0200, Adrian Bunk wrote:
> I'm looking for an easy way of getting the build dependencies of a
> package. At the moment I do look through the build log manually, and if I
> oversee something Roman Hodek sends a bug report that the m68k
> autobuilder found some mi
On Mon, Jul 24, 2000 at 04:23:22PM -0400, Matt Zimmerman wrote:
> On Mon, Jul 24, 2000 at 03:17:55PM +0200, Adrian Bunk wrote:
>
> > I'm looking for an easy way of getting the build dependencies of a
> > package. At the moment I do look through the build log manually, and if I
> > oversee someth
On Mon, Jul 24, 2000 at 03:17:55PM +0200, Adrian Bunk wrote:
> I'm looking for an easy way of getting the build dependencies of a
> package. At the moment I do look through the build log manually, and if I
> oversee something Roman Hodek sends a bug report that the m68k
> autobuilder found some m
> I'm looking for an easy way of getting the build dependencies of a
> package. At the moment I do look through the build log manually, and
> if I oversee something Roman Hodek sends a bug report that the m68k
> autobuilder found some missing build dependencies.
:-)
But to answer your question:
Hi,
I'm looking for an easy way of getting the build dependencies of a
package. At the moment I do look through the build log manually, and if I
oversee something Roman Hodek sends a bug report that the m68k
autobuilder found some missing build dependencies. Is there a more
comfortable way to get
> I'm looking for an easy way of getting the build dependencies of a
> package. At the moment I do look through the build log manually, and
> if I oversee something Roman Hodek sends a bug report that the m68k
> autobuilder found some missing build dependencies.
:-)
But to answer your question:
Hi,
I'm looking for an easy way of getting the build dependencies of a
package. At the moment I do look through the build log manually, and if I
oversee something Roman Hodek sends a bug report that the m68k
autobuilder found some missing build dependencies. Is there a more
comfortable way to get
8 matches
Mail list logo