Re: Question about license file
Hi >wifite.py has the license statement in the header, IMHO this is sufficient. after looking at the github repo, I see the project is made of a single py file, so the internal statement might be good already! Anyway, I opened an "upstream" issue [1] >It should be no problem to create a tarball manually. >The version in this case can be something like 2.0.85~gitedbdedd14 "create a tarball manually" is something that can be avoided with github projects www.github.com/user/project/tarball/branch << this gives you the tarball of latest commit of the branch named "branch" e.g. https://github.com/derv82/wifite/tarball/master and... yes, I'm really lazy! [1]https://github.com/derv82/wifite/issues/90 G.
Re: Question about license file
On 07/22/2016 05:00 PM, Daniel Echeverry wrote: > Hi Mentors! > > I am Maintainer of wifite[1][2], Some time ago the upstream migrated > the project to github[3] and made some Commits. I want update wifite > with these new changes, but in github repo, the upstream doesn't > include a license file, and he hasn't published any tarball. I tried > contact with the upstream to include a license file in the repo, but I > can't get answer for several months :( wifite.py has the license statement in the header, IMHO this is sufficient. > > How can I update wifite with the news changes? Can I make the patch > with the new changes?? It should be no problem to create a tarball manually. The version in this case can be something like 2.0.85~gitedbdedd14 Regards, Alex
