| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
tarball: dpibreak-x.y.z-unknown-linux-musl.tar.gz
distname: dpibreak-x.y.z
|
| |
|
|
| |
This was very log lived bug. Finally fixed.
|
| |
|
|
|
|
| |
Since commit 7f5456b ("windows: pull windivert-0.6.0 to local crate/
dir from crates.io"), the workspace layout changed and the version
detection in Makefile no longer finds the right Cargo.toml.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`make install` used to fail when run from a release tarball because
$(PROG) were depend on $(TARGET) but recipie for $(TARGET) were not
there. Decoupling build and installation by removing that dependancy.
Additionaly, there was verbose error messages Cargo.toml and git
metadata were not available on release tarball. Reorganized execution
order so that install/uninstall target no longer depends on cargo or
git.
Reported-by: dilluti0n <[email protected]>
Link: https://github.com/dilluti0n/dpibreak/issues/4
Fixes: #4
|
| | |
|
| | |
|
| |
|
|
|
|
| |
When installing, build should not happen both inside of release
tarball and repository (cargo build with root user is kinda
complexed).
|
| | |
|
| | |
|
| | |
|
| |
|