dcuddeback / libudev-rs Goto Github PK
View Code? Open in Web Editor NEWRust wrapper for libudev
License: MIT License
Rust wrapper for libudev
License: MIT License
Is @dcuddeback available and willing to transfer ownership of this repository and the associated project on crates.io?
Hey there,
I am currently starting to write some lipinput bindings, because there are no decent ones on crates.io and I will eventually need some for https://github.com/vberger/smithay.
Libinput contexts can (and most of the time should) be initialized by providing a udev context.
I would like to use this library for udev integration, but I need access to the raw context pointer to do call the corresponding libinput ffi functions.
I would like to ask you to expose some (maybe unsafe?) functions to get access to those?
Greetings,
Drakulix
Easiest for other libraries to use this using releases instead of git addresses. Necessary for dcuddeback/serial-rs#13
Your implementation makes some mistakes that pyudev made too, that were eventually discovered by means of extensive testing.
Two that I think I see in this implementation that pyudev used to make are:
I'm happy to refer you to more specific information if you are interested.
This issue was automatically generated. Feel free to close without ceremony if
you do not agree with re-licensing or if it is not possible for other reasons.
Respond to @cmr with any questions or concerns, or pop over to
#rust-offtopic
on IRC to discuss.
You're receiving this because someone (perhaps the project maintainer)
published a crates.io package with the license as "MIT" xor "Apache-2.0" and
the repository field pointing here.
TL;DR the Rust ecosystem is largely Apache-2.0. Being available under that
license is good for interoperation. The MIT license as an add-on can be nice
for GPLv2 projects to use your code.
The MIT license requires reproducing countless copies of the same copyright
header with different names in the copyright field, for every MIT library in
use. The Apache license does not have this drawback. However, this is not the
primary motivation for me creating these issues. The Apache license also has
protections from patent trolls and an explicit contribution licensing clause.
However, the Apache license is incompatible with GPLv2. This is why Rust is
dual-licensed as MIT/Apache (the "primary" license being Apache, MIT only for
GPLv2 compat), and doing so would be wise for this project. This also makes
this crate suitable for inclusion and unrestricted sharing in the Rust
standard distribution and other projects using dual MIT/Apache, such as my
personal ulterior motive, the Robigalia project.
Some ask, "Does this really apply to binary redistributions? Does MIT really
require reproducing the whole thing?" I'm not a lawyer, and I can't give legal
advice, but some Google Android apps include open source attributions using
this interpretation. Others also agree with
it.
But, again, the copyright notice redistribution is not the primary motivation
for the dual-licensing. It's stronger protections to licensees and better
interoperation with the wider Rust ecosystem.
To do this, get explicit approval from each contributor of copyrightable work
(as not all contributions qualify for copyright, due to not being a "creative
work", e.g. a typo fix) and then add the following to your README:
## License
Licensed under either of
* Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
* MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)
at your option.
### Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.
and in your license headers, if you have them, use the following boilerplate
(based on that used in Rust):
// Copyright 2016 libudev-rs Developers
//
// Licensed under the Apache License, Version 2.0, <LICENSE-APACHE or
// http://apache.org/licenses/LICENSE-2.0> or the MIT license <LICENSE-MIT or
// http://opensource.org/licenses/MIT>, at your option. This file may not be
// copied, modified, or distributed except according to those terms.
It's commonly asked whether license headers are required. I'm not comfortable
making an official recommendation either way, but the Apache license
recommends it in their appendix on how to use the license.
Be sure to add the relevant LICENSE-{MIT,APACHE}
files. You can copy these
from the Rust repo for a plain-text
version.
And don't forget to update the license
metadata in your Cargo.toml
to:
license = "MIT OR Apache-2.0"
I'll be going through projects which agree to be relicensed and have approval
by the necessary contributors and doing this changes, so feel free to leave
the heavy lifting to me!
To agree to relicensing, comment with :
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Or, if you're a contributor, you can check the box in this repo next to your
name. My scripts will pick this exact phrase up and check your checkbox, but
I'll come through and manually review this issue later as well.
It's supported in libudev, but needs to be exposed. This is necessary for dcuddeback/serial-rs#14.
The relevant function is struct udev_device * udev_device_get_parent(struct udev_device *udev_device);
.
I've tried hacking at this a bit, but this FFI stuff is super confusing considering how new I am to Rust
Hey there!
I have tried to build libudev-rs for the wasm32-wasi target and it was successful. However, building an application using it as a dependency fails on a linking stage. It says that it cannot find library: -ludev
. I am using Ubuntu 18.04 (WSL) and have libudev1 and libudev-dev packages installed.
Thanks!
The compiler's lifetime defaulting appears to produce this:
impl<'a> Enumerator<'a> {
fn scan_devices<'b>(&'b mut self) -> Result<Devices<'b>>;
}
Is that intentional? Naively, I would expect the enumerated devices to be valid even after the enumerator is gone. I didn't find any official libudev documentation about this however.
It sure would be a lot more convenient if this function returned a Devices<'a>
.
hello, Is this repository still maintained?
There does not seem to be any way to store a MonitorSocket
along with the corresponding Context
in a structure.
This would be useful in the scenario where the underlying fd
of the MonitorSocket
is registered with an eventloop and a struct
is used to store state used in the callback invoked by the eventloop.
libudev exposes functionality around monitoring for device changes that seem to be in libudev-sys, but aren't wrapped in libudev-rs. Would it be possible to have them added?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.