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

Tagged release? #22

Closed
sbrun opened this issue Jul 9, 2015 · 1 comment
Closed

Tagged release? #22

sbrun opened this issue Jul 9, 2015 · 1 comment

Comments

@sbrun
Copy link

sbrun commented Jul 9, 2015

Hello,
For a possible next release it would be great take a tagged release in git.
In kali we have tools that monitors web pages listing release, and it works well with github pages showing git tags. If you make a tagged release we will be automatically informed and we will update the package quickly.
Thanks

@p4r4n0y1ng
Copy link
Collaborator

We did this (sort of) within the code itself on Automater .21 and .211 (new releases). Based on the fact that many people use the tool, but want it to be "quiet" there are command line switches required, but basically it checks MD5 of all the modules if you run a -V on the command line. You also would need a -v to make it (verbose) talk to you in stdout. It would then report if there were changes between your local and the ones here on GitHub. Also, there is a new method of keeping your XML up to date. Basically if you run a -r, Automater will check for the tekdefense.xml file here versus the one on your local machine (if there's one there) and it will download it and use it in conjunction with your sites.xml file. This ensures you keep up to date with changes here that Ian makes to the XML, but also gives you that local sites.xml file to use as well! Pretty cool! In .211 there is collision checking between the 2 XML files too, and your local wins. All in all, you'll love it I think. Thanks for this suggestion!

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