-
Notifications
You must be signed in to change notification settings - Fork 427
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
Please rename drive to something less generic #271
Comments
Hello @sbrun, thank you for reporting this issue and welcome to drive! In response to your request: I don't think this is an issue because the project has been around for the last two years (however 7 months with my fork) without conflicting with other projects. Please let me know what you think. |
Hello, Thanks for your answer. Le 04/07/2015 11:21, Emmanuel Odeke a écrit :
|
@rhertzog fyi |
FWIW, the corresponding request to add a package generated quite some discussion about the name. You can check it out here: https://lists.debian.org/debian-devel/2015/07/threads.html#00023 We were going to rename the package to google-drive before integrating it in Debian anyway. But we will stop pursuing this "Intent to package" as it is much more work than anticipated. |
Thanks for the heads up @shaggytwodope. However, I think I'll let @sbrun make that decision on how to close it since her issue came first and spawned the entire Debian thread. |
@odeke-em Given the discussion in the Debian thread, if I have to sponsor someone to add drive to Debian I would ask him to rename the package and the binary to something less generic. Given that you did not seem to agree, we intended to pick a name ourselves: "google-drive". Now it's up to you to see whether you want to rename your software or not. If not, close this ticket. If you need more time to think about it, leave it open. |
@rhertzog gotcha. Am still hesitant on renaming it but feel free to rename it on the packaging end. Thing is the manifesto is to be able to add other backends in the future: ownCloud, s3, Dropbox, Azure etc and this is alluded to in the README. Switching the entire project's name to |
Btw Go binaries get their name from the directory they are stored in, so it wouldn't require naming the entire project, just a sect of it and throwing in a directory. Let me push up a PR that will enable this and the issue should be resolved. I think the original issue title should have been change the binary name :) |
Hello @odeke-em |
Reading the mailinglist over at debian I saw the idea of calling it odeke-drive. I kinda dig that... even tho @odeke-em is a terrible name (j/k mate :-p) go-drive could also be an idea for the debian pacakge. But I'am terrible with names, my first dog was named Doggy... |
@shaggytwodope hahaha. $ go get -u github.com/odeke-em/drive/google-drive
$ # OR
$ go get -u github.com/odeke-em/drive/drive-gen && drive-gen google-drive # To bundle debug info And now the binary should be google-drive. Please let me know if that solves your problem. |
Am off to bed for now, but I'll be back up shortly. |
Ping in case anyone has any thoughts. |
Just changed the alternate binary to |
Closing this issue since you can now generate a binary called |
Hi @odeke-em , sorry for reviving this topic, I run successfully the command: But drive-google is not being recognized as a command. This still works for Debian? Cheers! |
@Vamoss check if your environment variables are set correctly, as mentioned in the install docs: Setting these fixed the issue for me. |
Hi,
I'm in the process of packaging drive for debian. As Guillem commented in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790933#10 the name drive is very generic. It would be better to use another name to avoid conflicts with local commands using such generic names (or with other random software that people install from the net).
I would suggest "google-drive" or "gdrive" or something similar. What do you think ?
Thank you for considering my request.
The text was updated successfully, but these errors were encountered: