mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sweeney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-684) Automate publishing of artifacts with release candidates and releases
Date Fri, 27 Dec 2013 19:30:52 GMT

    [ https://issues.apache.org/jira/browse/MESOS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857662#comment-13857662
] 

Kevin Sweeney commented on MESOS-684:
-------------------------------------

It looks like the sdist created by python setup.py sdist currently hardcodes the buildroot
of the mesos source tree. Using an sdist I created with

{noformat} 
% ./bootstrap
% ./configure
% make
% make install
% cd src
% python python/setup.py sdist
% cp python/dist/mesos-0.16.0.tar.gz ~
{noformat}

The build fails with an error message
{noformat}
% tar zxvf mesos-0.16.0.tar.gz
% cd mesos-0.16.0
% python setup.py install
Traceback (most recent call last):
  File "setup.py", line 58, in <module>
    for file in os.listdir(os.path.join(abs_top_srcdir, src_python_native))
OSError: [Errno 2] No such file or directory: '/Users/ksweeney/workspace/mesos/src/python/native'
{noformat}

In theory as long as {{make install}} (or the OS package manager) installed appropriate header
files and a library that works with {{-lmesos}} it shouldn't be necessary to know about the
path that the {{make dist}} tarball was originally extracted to in order to compile the Python
bindings. I suspect the issue right now is that the Python egg is built before the libraries
and headers are installed at the expense of a {{setup.py}} that can't be used to create a
pip-compatible sdist.

> Automate publishing of artifacts with release candidates and releases
> ---------------------------------------------------------------------
>
>                 Key: MESOS-684
>                 URL: https://issues.apache.org/jira/browse/MESOS-684
>             Project: Mesos
>          Issue Type: Sub-task
>            Reporter: Vinod Kone
>             Fix For: 0.16.0
>
>
> Currently, when we tag a release candidate, we never upload the relevant artifacts (e.g.,
mesos jar) for the community to be able to test it. It would be great if we can have a script
to automate this.
> Since we also support Python, we could (should?) also publish a mesos egg to somewhere
in Apache?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message