Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Switch to using external pex skylark rules #1114

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

benley
Copy link

@benley benley commented Jul 20, 2016

Fixes #1032

Hopefully this doesn't break compatibility with Bazel 0.2.3

"pex_pytest",
)
load(
"@bazel_tools//tools/build_defs/pkg:pkg.bzl",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is @bazel_tools defined globally somewhere and is this the proper way to reference the pkg targets we need? I see where @io_bazel_rules_pex is defined, but not @bazel_tools.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe @bazel_tools is defined internally by Bazel; it replaces the former implicit merging of //tools into the user workspace.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with 0.3.0 @bazel_tools is not supported I believe. Our repo can compile both in bazel 0.2.3 and bazel 0.3.0. Can you please ensure that it compiles with bazel 0.3.0 as well?

Copy link
Author

@benley benley Jul 20, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm doing all my development and testing on 0.3.0 so far. @bazel_tools does work there.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool - travis ci works with bazel 0.2.3

@kramasamy
Copy link
Contributor

@benley - any updates on this?

@objmagic objmagic added the build label Aug 4, 2016
@benley
Copy link
Author

benley commented Aug 9, 2016

Sorry for disappearing; I haven't had time to work on this in the past week, but I intend to get back to it fairly soon.

@objmagic
Copy link
Contributor

hi @benley, any update on this PR?

@benley
Copy link
Author

benley commented Oct 18, 2016

Not much news, but I think I know of a reasonably sane way of publishing a usable source archive via pypi for the pex rules, which should remove the main obstacle. I'll try to make progress on this issue this week.

@kramasamy
Copy link
Contributor

@benley - any progress on this?

@kramasamy
Copy link
Contributor

@benley - wondering if you would like to merge these rules into Bazel?

@benley
Copy link
Author

benley commented Jun 19, 2017

Hi there, sorry I have gone silent for so long. I changed jobs and have not had much time to work on bazel-related things recently.

It would be cool to get the pex rules hosted under the bazelbuild project, but I don't think they will be interested because it more or less duplicates the functionality of https://github.com/google/subpar, along with bazel's built-in Python rules.

I did work out a way of hosting skylark rules on pypi, though! https://pypi.python.org/pypi/bazel-rules-pex

@kramasamy
Copy link
Contributor

kramasamy commented Jun 19, 2017

Thanks @benley - we could take care of maintaining the rules. The only issue that I am facing with it - when I run it the first time I get some errors. However, if we run bazel again, it seems to work. Not sure what is the issue - if you could help, it will be great.

benley/bazel_rules_pex#37

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants