On Sat, Feb 07, 2015 at 09:54:58 -0800, Petr Skočík wrote:
> I found it -- this might kind of be a `tup` bug too.
> Basically, bundle tries to look for `gemspec` files in certain folders
> recursively. The recursive search is done with `Dir['{,*,*/*}.gemspec']`
> which triggers `open/openat` with
> `O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC` calls for each file/directory.
> Since the O_DIRECTORY flag causes these calls to immediate fail on
> nodirectory entries, `tup` shouldn't register these open calls open calls
> that set up a dependency.
So Tup should track whether a potential open() is *impossible* and
ignore it? That's going to be some fun logic, what with chasing down the
kernel version and valid flags, flag combinations, etc. :) . For each
supported platform.
What if a directory by one of the names attempted shows up in the
future and therefore making the open valid? Tup's model states it should
rerun.
Is it possible to run bundler with an explicit list of gemspec files?
--Ben
--
--
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.
