https://pantsbuild.org/ logo
Powered by
#general
  • h

    hallowed-computer-65556

    05/09/2017, 5:49 PM
    oh you guys 🙂
  • h

    hallowed-computer-65556

    05/09/2017, 5:49 PM
    Now having flashbacks to Mesos 1st generation config files written by devs 🙂 but i’ll save that for the PTSD slack
  • h

    hallowed-computer-65556

    05/09/2017, 5:52 PM
    i’ll give that a whirl and see if it gives us a simple solution
  • w

    witty-crayon-22786

    05/09/2017, 5:53 PM
    nick's suggestion is cleaner, and is how things like https://github.com/foursquare/fsqio/ and https://github.com/twitter/commons (out of date as it is) separate "internal config" from "external config"
  • w

    witty-crayon-22786

    05/09/2017, 5:54 PM
    but yea, a few tools here.
  • w

    witty-crayon-22786

    05/09/2017, 5:54 PM
    it's why BUILD file suffixes exist.
  • h

    hallowed-computer-65556

    05/09/2017, 5:55 PM
    No surprise to you maybe, but the docs need more examples and fewer words. if i keep using pants (I’m switching projects in a major way soon so dunno) I will try to offer some
  • w

    witty-crayon-22786

    05/09/2017, 5:56 PM
    that would be appreciated. it's a github PR workflow now, so pretty straightforward.
  • h

    hallowed-computer-65556

    05/09/2017, 5:56 PM
    I’ll try it Nick’s way. So I’m going to have two BUILD files in the OS project. I suppose that’s cleaner than having one in the target where the private files is. and we have to just instruct people to make this file. Again though there is this problem — that file isn’t in version control anywhere. I mean, it could be aliased but some people find that dirty too.
  • w

    witty-crayon-22786

    05/09/2017, 5:57 PM
    could configure it as ignored internally, although that might just move the problem
  • w

    witty-crayon-22786

    05/09/2017, 5:58 PM
    --build-ignore=['the/BUILD.file_i_want_to_ignore']
  • h

    hallowed-computer-65556

    05/09/2017, 5:59 PM
    what i want is the opposite of that.. --build-also-include-this-other-thing <thing>
  • w

    witty-crayon-22786

    05/09/2017, 5:59 PM
    if you ignore it in one place, but don't ignore it in the other...?
  • w

    witty-crayon-22786

    05/09/2017, 7:53 PM
    @fancy-queen-20734 , @limited-country-20626 : can you take a peek at https://github.com/pantsbuild/pants/pull/4572
  • l

    limited-country-20626

    05/09/2017, 7:54 PM
    yah, looking now
  • l

    limited-country-20626

    05/09/2017, 7:57 PM
    We have 
    BUILD
    and 
    BUILD.opensource
    to differentiate targets that way, works fine
  • c

    curved-manchester-66006

    05/09/2017, 8:07 PM
    I see that golang support is in contrib, and knowing nothing about go but something about pants I was able to transform a prototype transformation of a go project to pants and the result looked more civilized from my perspective. For a monorepo that will be almost entirly go, is Pants a strong contender versus bazel/some_go_specific thing?
  • w

    witty-crayon-22786

    05/09/2017, 8:08 PM
    @curved-manchester-66006 : iirc, a few shops have been using it.
  • h

    hallowed-computer-65556

    05/09/2017, 8:08 PM
    I see what yr getting at @witty-crayon-22786 . But this still creates a gap for someone else building against their own config file that should live safely in a repo too . Just had a chat and we're going to go the env var route for now
  • w

    witty-crayon-22786

    05/09/2017, 8:08 PM
    it's in a slightly better "i do all my development using $lang with pants" state than node.js is
  • h

    hallowed-computer-65556

    05/09/2017, 8:09 PM
    Thanks for the advice
  • w

    witty-crayon-22786

    05/09/2017, 8:09 PM
    np.
  • c

    curved-manchester-66006

    05/09/2017, 8:10 PM
    ha, a distant second language of interest is nodejs, but that ecosystem is... complicated
  • c

    curved-manchester-66006

    05/09/2017, 8:12 PM
    Is it more "missing useful features" or "this is totally archaic; don't code this way anymore" like the old python backend (I know it's a vague question, thank you for the color commentary)
  • w

    witty-crayon-22786

    05/09/2017, 8:18 PM
    @curved-manchester-66006 : my second-hand take is that go's tooling alone is very, very snappy
  • w

    witty-crayon-22786

    05/09/2017, 8:18 PM
    and pants adds some overhead there.
  • w

    witty-crayon-22786

    05/09/2017, 8:19 PM
    ...compared to manually vendoring everything, for example
  • w

    witty-crayon-22786

    05/09/2017, 8:19 PM
    that's the kind of stuff we hope to address with the daemon though (now in alpha!)
  • w

    witty-crayon-22786

    05/09/2017, 8:20 PM
    . @happy-kitchen-89482 might have a better take there
  • l

    limited-country-20626

    05/09/2017, 8:28 PM
    we are starting to consume the go plugin
1...172817291730...2420Latest