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

Documentation: define what is "install" in Meson terms #8479

Open
denizzzka opened this issue Mar 5, 2021 · 3 comments
Open

Documentation: define what is "install" in Meson terms #8479

denizzzka opened this issue Mar 5, 2021 · 3 comments

Comments

@denizzzka
Copy link

denizzzka commented Mar 5, 2021

Current manual:
https://mesonbuild.com/Installing.html

What Meson means by the "install"? Really, it's not at all obvious

@eli-schwartz
Copy link
Member

Meson uses the same terms everyone else uses, as far as I'm aware.

It's not obvious to me, which second definition you're aware of, that people might confuse things with.

@denizzzka
Copy link
Author

Meson uses the same terms everyone else uses, as far as I'm aware.

everyone else == "make install"? I am neofite and I don't know what make install actually does (some relict behaviour what currently tries to broke my package system?))

I am not trolling here. I think it is need to (briefly) describe why and what for build system (which producees binaries etc) acts as package system of my OS (if you mean this)

@eli-schwartz
Copy link
Member

Ninja install acts exactly like make install.

Make install acts exactly like apt install (or rpm, or emerge, or pacman, or xbps-install), except without centralized management so you don't get validation of OS package manager dependencies.

OS package managers traditionally run make install to install the software, but then record what got installed and turn those records into OS packages.

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