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

The need to install a long list of packages even before tebako setup can be run is unfriendly #60

Open
maxirmx opened this issue Dec 21, 2021 · 2 comments

Comments

@maxirmx
Copy link
Member

maxirmx commented Dec 21, 2021

@ronaldtse:
the need to install a long list of packages even before tebako setup can be run is unfriendly

@maxirmx
Copy link
Member Author

maxirmx commented Dec 21, 2021

Practically there are several options to do it:

a. Use apt to install from standard sources. The good practice is to require user to do it manually because such packages may change global OS environment and it is better at least to try user to understand what he is doing

b. Compile in-place without altering global environment. We can do it since we need static libraries only. ruby-packer installs its required packages this way but ruby packer needs only 7 packages that it compiles for 40 minutes. We require ~20 and it will take 3-4 hours

c. Use docker or other virtual environment so that everything we need can be installed silently without effect to global environment

d. Deploy by setup script silently into manually created virtual environment using something like 'apt-get download package; dpkg -i --force-not-root --root=$HOME package.deb'
As far as I understand bundler or pip or npm do it when they cannot apply sudo
Of cause this is OS specific solution in a sense that it is different accross Linux/MacOS/Windows

e. Use advanced package manager like vcpkg that is able to create isolated environment. The issue here is that vcpkg will build a lot of things in-place and everything starting from cmake and it will take hours. Probably more then option b.

f. Invent something new

Right tebako requires method a, which is the simpliest and the most acceptable for alfa version (aka proof of concept). The reason is very simple - it allows to make manual changes fast with extra overhead.

@ronaldtse
Copy link
Contributor

a. Use apt to install from standard sources.

This is not the issue I'm concerned about. Installing dependencies is generally not a problem. We can always replace this step with a single bash script that makes it simpler.

Like how Cmake does it with:

curl https://apt.kitware.com/kitware-archive.sh | bash

We should definitely offer this.

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

No branches or pull requests

2 participants