question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

.buckconfig [project]: ignore 1 file, but not others with the same name

See original GitHub issue

Background:

We have our own buck wrapper script checked in as ./buck in our project root. We also have a lot of developers on OSX who have case-insensitive filesystems.

Our old version of buck was somehow able to realize that ./buck was not a BUCK build file, even despite the case-insensitivity of the filesystem, but upon upgrading buck, we now get an error message about how it can’t parse the shell script as a BUCK build file.

The options we came up with were:

  1. forcing everyone to create a case-sensitive partition (painful)
  2. renaming ./buck to something like ./buckw (would require us to change a large number of deployment and testing scripts, and get developers used to the new name of the command)
  3. ignore buck inside .buckconfig, like so:
[project]
  ignore = buck

Unfortunately, the 3rd option didn’t seem to actually work: even on my case-sensitive filesystem, buck began ignoring changes to actual BUCK build files! Is there a way I could ignore just the file I want? (./buck didn’t seem to work…)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
styurincommented, Nov 2, 2017

It seems like this problem is specific to one project only and we don’t really want to support cases like this.

As to your problem, you can rename all BUCK files to something else thought it might be too disruptive to do.

My recommendation is to pay one time cost of moving ./buck to something else rather dealing with workarounds. The more time use spend with that the more problems you’ll have later.

get the file to be syntactically correct in both bash and python.

We are moving to Skylark soon and it can break with that migration.

0reactions
jiangty-addeparcommented, Nov 2, 2017

Thanks for the recommendations! I’ll probably do hack option 4 for now and figure out a transition plan for renaming ./buck after I finish the upgrade.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Buck: .buckconfig
This speeds up builds for large projects over using regular directory header search paths, but breaks some Xcode features, like header file name...
Read more >
What does // refer to when you have nested Buck projects?
In BUCK file C, I have a path like this: //:library . When not used as a submodule, // will be resolved to...
Read more >
Gerrit Code Review - Building with Buck
Gerrit Development WAR File; Headless Mode; Extension and Plugin API JAR Files; Plugins; Documentation; GWT Compile Report; Gerrit Release WAR File.
Read more >
Buckaroo Documentation - Read the Docs
All logs are transferred over HTTPS and are not shared with any third-party. What is Shared? ... update the project's .buckconfig file.
Read more >
Building With Buck + Travis CI
So you have a Buck based project and want to use Travis as your CI, ... will not be using Homebrew in this...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found