Ah, one thing: I think there were drawbacks with using
RUN_DEPENDS = ${BUILD_DEPENDS}
so best to duplicate them here.
I think pre-build can be smarter, i.e.
cd ${WRKSRC}/lib/ && find . -name \*.whl -exec env pip ... {} +
But I can't test that right now, so OK kn for the updated p
On 11/22, Stuart Henderson wrote:
> On 2020/11/22 16:45, Klemens Nanni wrote:
> > On Sun, Nov 22, 2020 at 02:42:16AM +0300, Pavel Korovin wrote:
> > > I'm looking for OKs to import this.
> > `make test' works with two small warnings, "devel" should probably be
> > the primary category instead of "s
On 2020/11/22 16:45, Klemens Nanni wrote:
> On Sun, Nov 22, 2020 at 02:42:16AM +0300, Pavel Korovin wrote:
> > I'm looking for OKs to import this.
> `make test' works with two small warnings, "devel" should probably be
> the primary category instead of "sysutils".
sysutils is more descriptive, see
On Sun, Nov 22, 2020 at 02:42:16AM +0300, Pavel Korovin wrote:
> I'm looking for OKs to import this.
`make test' works with two small warnings, "devel" should probably be
the primary category instead of "sysutils".
Where do those LOCAL_DEPS come from? How did yoy compile that list?
I'd be helpful
Dear all,
I'm looking for OKs to import this.
$ pkg_info py3-vsphere-automation
Comment:
VMware vSphere Automation SDK for Python
Description:
VMware vSphere Automation SDK for Python
Maintainer: Pavel Korovin
WWW: https://github.com/vmware/vsphere-automation-sdk-python
--
With best regard
