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

Include license in strings #46

Closed
jakirkham opened this issue Aug 9, 2016 · 4 comments
Closed

Include license in strings #46

jakirkham opened this issue Aug 9, 2016 · 4 comments

Comments

@jakirkham
Copy link

One of the nice things about tini is it is so nice to install. Merely download the executable and one is good to go.

However, there is a fair point that the license file should be included to. In order to keep things simple, would it be possible (or even reasonable) to have the license reproduced as a string in the final binary (e.g. visible via strings). This should be pretty easy to do. Just wondering if this would be ok.

@krallin
Copy link
Owner

krallin commented Aug 10, 2016

@jakirkham I think this makes a lot of sense. Thanks for bringing this to my attention. I hadn't realized my license was asking users to redistribute it while my instructions were inviting them not to..!

Can you check #47 (and specifically the one commit in there that adds the license) and let me know whether you feel that would work for you?

@krallin
Copy link
Owner

krallin commented Aug 10, 2016

For the sake of clarity; the output's going to look like this:

root@784c7c2ea28e:/# tini
tini (version 0.9.0 - git.203835d-dirty)
Usage: tini [OPTIONS] PROGRAM -- [ARGS]

Execute a program under the supervision of a valid init process (tini)

  -h: Show this help message and exit.
  -s: Register as a process subreaper (requires Linux >= 3.4).
  -v: Generate more verbose output. Repeat up to 3 times.
  -g: Send signals to the child's process group.
  -l: Show license and exit.

root@784c7c2ea28e:/# tini -l
The MIT License (MIT)

Copyright (c) 2015 Thomas Orozco <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

@jakirkham
Copy link
Author

This is a nicer proposal then even the one I had in mind. Though this definitely seems like the right way to go. Thanks for coming up with this @krallin.

@krallin
Copy link
Owner

krallin commented Aug 12, 2016

Closed in #47

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