On Wed, Oct 27, 1999 at 03:17:52PM +0100, Julian Gilbey wrote:
> Firstly, that if we are now demanding build-time dependencies, we are
> asking maintainers to do a *lot* of work. (This took me about 2
> hours, maybe a little bit more.) We ought to think of a better way of
> performing this task i
On Wed, Oct 27, 1999 at 03:17:52PM +0100, Julian Gilbey wrote:
> Finally, a small point. It may be worth stating that if a package is
> required to satisfy an (install-time) dependency of a listed
> dependency, then it does not need to be listed itself. Although,
> having said this, I think this
Julian Gilbey <[EMAIL PROTECTED]> writes:
> OK, I've just tried to calculate the build-time dependencies for
> debian-policy, and here are some thoughts.
>
> It's not easy. In fact it's *really* not easy.
>
> I first tried running strace on the build process, but due to the
> presence of a vfor
> It seems you have not read the amendment. There was a mechanism for
> this even in the first draft.
>
> And I would have appreciated these comments at the proposal stage, when
> we were still hammering out the thing. I even called for people with
> complicated packages to give their input when
On Wed, Oct 27, 1999 at 03:17:52PM +0100, Julian Gilbey wrote:
> It's not easy. In fact it's *really* not easy.
It is easy. I've specified build-time dependencies on some of my packages
for months now. You just happened to try a nasty case as your first.
> Standard packages: dpkg-dev, lynx, ma
On Wed, Oct 27, 1999 at 03:17:52PM +0100, Julian Gilbey wrote:
> OK, I've just tried to calculate the build-time dependencies for
> debian-policy, and here are some thoughts.
>
> It's not easy. In fact it's *really* not easy.
When I came up with a simple implementation awhile back, the fakeroot
> OK, I've just tried to calculate the build-time dependencies for
> debian-policy, and here are some thoughts.
>
> It's not easy. In fact it's *really* not easy.
If you really want to (more or less) automate it, it's really not
easy... But for most packages, src-deps are rather clear. It seems
OK, I've just tried to calculate the build-time dependencies for
debian-policy, and here are some thoughts.
It's not easy. In fact it's *really* not easy.
I first tried running strace on the build process, but due to the
presence of a vfork, I missed most of the interesting stuff.
So strace is n
8 matches
Mail list logo
