On Thu, Apr 20, 2017 at 8:30 AM, Samuel Williams <[email protected]> wrote: > Hi. > > I'm the author of teapot - http://teapot.nz/welcome/index and also > interested in build tools. > > Teapot uses a global DAG within reason - it's not possible to know how an > external project builds itself.. but I've been thinking, at the very least I > could track what files it installs to know it's specific outputs even though > they are not described completely in the initial DAG. > > A more concrete example would be - what headers does libpng install when > running `make install`. Teapot supports invoking external build systems. But > we don't know a lot about what outputs would be produced. > > How does tup handle these situations?
Hi Samuel, Tup isn't designed to handle packaging, so it doesn't feature things like 'make install' that would commonly be used as part of a "configure/make/make install" type of package distribution. It's more geared for developers to iterate the edit/compile/test cycle of a project quickly. I believe package maintainers that generate RPMs & .debs run the builds in isolated environments to track what files are installed, but I'm not familiar with those details. It sounds like teapot might be more closely related to the latter? -Mike -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
