Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install-binaries.sh violates distro packaging guidelines #340

Open
flaviut opened this issue Jul 5, 2019 · 1 comment
Open

install-binaries.sh violates distro packaging guidelines #340

flaviut opened this issue Jul 5, 2019 · 1 comment

Comments

@flaviut
Copy link
Contributor

flaviut commented Jul 5, 2019

  • what are you trying to do?

Install scrimmage

  • what is the problem and how can it be recreated?

sudo ./setup/install-binaries.sh -e 0 -p 3

Note that pip install ... is run. This is not OK because it breaks the package manager when packages are installed in /.

See Debian-DontBreakDebian (emph mine):

When you install software this way, you will not be able to remove it with apt-get or Synaptic. The APT packaging system can only remove software that was installed by the APT packaging system. Even worse, software installed this way can sometimes conflict with the software packaged for Debian.

Every distro has a similar disclaimer.

  • what scrimmage commit are you on? You can see this with git rev-parse HEAD

a84c0f3

@SyllogismRXS
Copy link
Contributor

Do you suggest we install debian packages of the python packages that we require (e.g., apt-get install python-<somepackage)? We could also update the instructions to have the user create a python virtual environment when installing scrimmage. I want to get rid of the install-binaries script eventually and just have the user install scrimmage-dependencies, which references the specific debian packages that are required.

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

No branches or pull requests

2 participants