License is being installed to `/usr/LICENSE`
See original GitHub issuepython setup.py build
python setup.py install --optimize=1 --skip-build
This generates a LICENSE
file in /usr
which is super weird.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to obtain license or installation number
This help article will guide you through how to find your license number after the license has been installed on your system.
Read more >Chapter 2 License Management (Sun WorkShop Installation ...
The license file, or a copy of it, must be accessible to every machine running the licensed software and each machine designated as...
Read more >Installing Local (RLM) Licenses - Foundry Learn
- the easiest way to install a license is to use Foundry Licensing Utility (FLU). See Installing Licenses Automatically for more details. Manual...
Read more >Installing a New License Server - Sybase Infocenter
Installing a New License Server · Insert DVD into the appriopriate drive. · To install the SySAM Suite using the GUI tool, launch...
Read more >Before you install the license server - IBM
If you install the license server to the directory /opt/rational and the directory is owned by root, run the license_setup as root. For...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Done, thanks.
Just FYI, including
LICENSE
indata_files
is likely the issue, or at the very least an issue;data_files
is a a long deprecated, discouraged and unsafe way of distributing files outside the package tree that will eventually be fully removed, whereas thelicense_files
,license_file
andMANIFEST.in
(in that order) are all much more appropriate solutions, never mind that reasonably modern packaging tools (thanks to a feature I helped add) will includeLICENSE
as alicense_file
automatically. So I suggest simply eliding thedata_files
line, as there’s no need for it anymore and it can only cause problems.(I’m one of the maintainers of QtPy, BTW 😃