Package Details: way-cooler 1:0.8.1-1

Git Clone URL: https://aur.archlinux.org/way-cooler.git (read-only, click to copy)
Package Base: way-cooler
Description: Customizeable Wayland compositor written in Rust (upstream abandoned)
Upstream URL: https://way-cooler.org/
Keywords: way-cooler wayland windowmanager
Licenses: MIT
Submitter: vinipsmaker
Maintainer: alerque (timidger)
Last Packager: alerque
Votes: 22
Popularity: 0.000000
First Submitted: 2016-08-14 20:08 (UTC)
Last Updated: 2024-03-27 08:41 (UTC)

Dependencies (8)

Required by (1)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

vinipsmaker commented on 2017-01-15 22:50 (UTC)

@flagger: Done. Will do this to the git version as well in a moment.

flagger commented on 2017-01-15 22:11 (UTC) (edited on 2017-01-15 22:12 (UTC) by flagger)

Can you please add way-cooler.desktop from git to /usr/share/wayland-sessions/?

timidger commented on 2017-01-08 02:51 (UTC)

@wkunkel Weird, don't know why that error doesn't trigger with me when I try to build/install it locally... Fixed on master, I suggest you try https://aur.archlinux.org/packages/way-cooler-git until this fix is pushed with 0.4.2 (which will come on Monday)

rosekunkel commented on 2017-01-08 02:47 (UTC)

Installing via this package currently fails with compilation error: error: type alias is never used: `ValueResult` --> src/lua/rust_interop.rs:16:1 | 16 | type ValueResult = Result<AnyLuaValue, &'static str>; | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | note: lint level defined here --> src/lua/rust_interop.rs:2:9 | 2 | #![deny(dead_code)] | ^^^^^^^^^

timidger commented on 2017-01-02 20:42 (UTC)

@vinipsmaker Glad we came to an agreement. I understand where you're coming from, assuming everyone follows semvar correctly (and that we specify dependencies sanely in the Cargo.toml file) rebuilding the Cargo.lock DOES make sense because it gives the best improvements possible. Unfortunately, we don't live in a perfect world. Not everyone follows semvar (especially pre-1.0 crates, which is the majority of our dependencies), and sometimes people make mistakes. If a user reports an issue it can make debugging that much harder when their version of Way Cooler is not the same as the Way Cooler that is used by different distros. We try to keep on top of dependency updates though, updating the lock file every month. If you want, the "-git" version of the Way Cooler AUR package can continue to remove the Cargo.lock as that's supposed to be an "experimental"/cutting-edge version of Way Cooler already and it can be helpful if users of that report issues before we even deal with them.

vinipsmaker commented on 2017-01-02 19:09 (UTC)

@snirkimmington: this script is run to generate the package, not to install it. This is not how ArchLinux works. However, there was a possible improvement in the package (mark this file as a config file). Done too.

vinipsmaker commented on 2017-01-02 19:06 (UTC)

@timidger: > For binaries in Rust, the Cargo.lock should be upheld I thought a lot about this problem. If a dependency is updated, we want the updated (with possible security fixes) version. I thought and I thought. And my conclusion is: this is a problem of yours, not mine. I'll no longer remove the `Cargo.lock` file. You guys should release a new version of way-cooler with forced update on the affected dependencies specified in `Cargo.toml` itself. Anyways. Problem solved and we agree on the solution as it affects the ArchLinux package (remove `Cargo.lock`).

Valryne commented on 2016-12-09 11:37 (UTC)

Just installed current release (0.4.0) successfully: *) changed version info in PKGBUILD: pkgver=0.4.0 pkgrel=1 *) removed whole prepare() block as I don't see a reason to delete Cargo.lock

snirkimmington commented on 2016-09-19 17:22 (UTC) (edited on 2016-09-19 17:45 (UTC) by snirkimmington)

Also, please only copy the init.lua file to /etc/way-cooler/init.lua if there isn't one already there - we don't want to override init files. EDIT: Forgot that user customization will take place in $XDG_CONFIG_DIR. Overriding every time might be a good idea - we shouldn't be making any breaking changes but we need the best guarantee that if the user config fails the default will work.

timidger commented on 2016-09-19 17:14 (UTC)

For binaries in Rust, the Cargo.lock should be upheld (see [here](http://doc.crates.io/guide.html#cargotoml-vs-cargolock)). By removing it, this could make it more difficult to debug if it's a versioning issue.

« First ‹ Previous 1 2 3 4 Next › Last »