-
Notifications
You must be signed in to change notification settings - Fork 46
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
Added PhantomJS 1.6.1, OptiPNG 0.7.1 and libjpeg-turbo 1.2.1 #53
Conversation
Thanks, but I prefer that if you own the packages, you should have your own nugetpackages repository. It keeps down the confusion of where to go. Thoughts? |
Well, I was hoping to not 'own' these packages myself if possible ;0 Just trying to help out the Yeoman guys, by putting together the Windows support necessary to bootstrap Yeoman. We're going to lean on Chocolatey to install environmental pre-reqs (Rails and a few others). If it's too much of a burden I could take on hosting the .nuspecs under my account and hooking up the publish to the package directory. If I do that, I would probably create a generic account / key, and stuff that key in the repo with a PowerShell script to publish up to Chocolatey... so that in the event someone else takes them over, the info is there for them. Which would you prefer? |
I would leave out the key just for the fact that it creates a huge security risk - anyone would be able to upload those packages and could potentially put up a damaging package without fear of being caught. |
If you have not uploaded these packages I could take them on. |
I was under the impression that you already had them uploaded somewhere. |
No, I hadn't uploaded them. I realized re: key, which is why I mentioned it. I maintain a handful of Nuget proper packages already, but thought it might be best to have these packages maintained with the rest of the main Chocolatey packages, so that I'm not a single point of failure ;0 But if you're swamped, I can do it. |
totally up to you. I'm working on automating away almost all package updates so they happen automatically without a need for me to do anything other than let a computer run. |
Bringing you into yeoman/yeoman#216 |
I can merge these in and push it up later this week (or today). |
Haha -- yeah, not much left in the week ;0 |
Cleaned this up ... new pull req from a diff branch - Will be adding Yeoman itself in a minute. |
All of these will be needed for the upcoming Yeoman