Merge pull request #68 from pinage404/fix/binary-package-format

Fix/binary package format

README.md

@@ -56,7 +56,7 @@ yes
 `binstall` works with existing CI-built binary outputs, with configuration via `[package.metadata.binstall]` keys in the relevant crate manifest.
 When configuring `binstall` you can test against a local manifest with `--manifest-path=PATH` argument to use the crate and manifest at the provided `PATH`, skipping crate discovery and download.
 
-To get started, add a `[package.metadata.binstall]` section to your `Cargo.toml. As an example, the default configuration would be:
+To get started, add a `[package.metadata.binstall]` section to your `Cargo.toml`. As an example, the default configuration would be:
 
 ```toml
 [package.metadata.binstall]

src/main.rs

@@ -199,7 +199,11 @@ async fn main() -> Result<(), anyhow::Error> {
         // Generate install paths
         // Source path is the download dir + the generated binary path
         let source_file_path = bin_ctx.render(&meta.bin_dir)?;
-        let source = bin_path.join(&source_file_path);
+        let source = if meta.pkg_fmt == PkgFmt::Bin {
+            bin_path.clone()
+        } else {
+            bin_path.join(&source_file_path)
+        };
 
         // Destination path is the install dir + base-name-version{.format}
         let dest_file_path = bin_ctx.render("{ bin }-v{ version }{ format }")?; 
@@ -235,6 +239,12 @@ async fn main() -> Result<(), anyhow::Error> {
     for (_name, source, dest, _link) in &bin_files {
         // TODO: check if file already exists
         std::fs::copy(source, dest)?;
+
+        #[cfg(target_family = "unix")]
+        {
+            use std::os::unix::fs::PermissionsExt;
+            std::fs::set_permissions(dest, std::fs::Permissions::from_mode(0o755))?;
+        }
     }
 
     // Generate symlinks