-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing many times the same justfile. #2436
Comments
Thanks for opening an issue! You should be able to do I'm going to leave this open though, since I think possibly we should just detect this and avoid throwing an error in the first place. If you're importing the same recipe from the same file, then there's really no problem with allowing it, since the two recipes are identical. |
In fact, that's what I'd like to avoid doing. This case (when the import is the same file) should, IMO, not be handled with an "override" mechanism like "set allow-duplicate-recipes" (which is what, by the way, I am currently doing to work around this issue). The reason being that I'd like, precisely, to bail out when genuine duplicate recipes appear. In essence, I am turning off a safety mechanism to solve an issue that, IMO, should not exist in the first place. (But there is no hurry: I can live with the "set allow-duplicate-recipes" workaround.) |
This is implemented in #2437! Just will now ignore duplicate imports, so no need for |
Thank you ! P.S.: I just checked. Works like a charm. |
Hi.
I am writing some multiple just fragments to handle some aspects of my build systems. Some of them, say
A.just
andB.just
depend on another,C.just
. Essentially, I'd like to writeimport "A.just"
and/orimport "B.just"
. When I import only one of them, it works fine: A.just is importing C.just, or B.just is importing C.just. No conflict. When I import both of them, the tasks inC.just
conflict as they are declared twice, once for each import.Ideally, there should be some "caching" mechanism that would allow the C.just file to be detected to be the same, and thus imported only once. No ?
The text was updated successfully, but these errors were encountered: