ariatosca-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ran Ziv (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARIA-384) egg-info directory not cleaned during "make clean" and may cause stale dist
Date Thu, 14 Sep 2017 16:07:00 GMT
Ran Ziv created ARIA-384:
----------------------------

             Summary: egg-info directory not cleaned during "make clean" and may cause stale
dist
                 Key: ARIA-384
                 URL: https://issues.apache.org/jira/browse/ARIA-384
             Project: AriaTosca
          Issue Type: Bug
            Reporter: Ran Ziv


When using the [release script|https://github.com/apache/incubator-ariatosca/blob/master/release/asf-release.sh]
to create releases, it seems like in some cases the dist created may be "stale" e.g. after
updating the {{manifest}} file, if the {{egg-info}} directory exists in the top-level directory
of the project and is not cleaned.

The {{Makefile}}'s "clean" directive originally ran a command to clean the {{egg-info}} dir
- However it was removed, because if the directory is removed, any editable installations
of ARIA (i.e. "pip install -e" installations) will no longer detect the ARIA package as installed.

Rather than figuring out how to overcome this "staleness" problem, or alternatively cleaning
up {{egg-info}} during release creation and then setting the {{egg-info}} dir back up, it'd
probably be best to simply create releases on a separate, clean environment, where ARIA is
installed normally and not in editable mode.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message