FWIW, David Ebbo has a post on his blog about how to configure your own local copy of NuGet.exe to store the API key in its app.config file so that you needn't commit the API key to your repository (thus, sharing it with the world <g>).
Google it and it will turn up. Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Fri, Apr 1, 2011 at 11:35 PM, Nathan Palmer <[email protected]>wrote: > I just modified the build process to auto generate the .nuspec file and > subsequently the package as part of the build process. It's been pushed to > github. > > I actually feel that we should publish to nuget as part of the > build/release process. Even though it occurs each time changes are pushed > this is infrequent and if I'm working on a large set of changes it's > generally in a branch that wouldn't affect the release. I just need to > decide the best way to handle storing of the api-key and then I'll integrate > it. > > Thanks, > > Nathan Palmer > > > On Fri, Apr 1, 2011 at 6:16 PM, Miles Waller <[email protected]>wrote: > >> Hi, >> >> Thanks - Nathan, I've sent you the specs separately. >> >> Hopefully nuget will sort out the issue about version numbers/priorities >> sometime soon. Rhino.etl changes infrequently enough that I doubt there >> will be a problem with breaking downstream packages: as far as I can tell >> the binaries are so well hidden at the moment that most serious users have >> their own fork of the source anyway! >> Miles >> >> On Fri, Apr 1, 2011 at 1:32 PM, miles <[email protected]> wrote: >> >>> Hi, >>> >>> I've created a nuget package of the current rhino.etl trunk. >>> >>> It's pretty cool as it pulls in all the relevant boo, rhino.dsl, >>> filehelpers and log4net dependencies that are needed automatically, >>> from the other packages published there. >>> >>> I noticed that changes cause successful new builds to end up here: >>> http://builds.hibernatingrhinos.com/builds/Rhino-ETL >>> >>> Is there any mileage in getting the packages automatically fed to the >>> nuget feed at the same time? It doesn't look too hard, though I >>> didn't manage to get the powershell-based build to work at all. >>> >>> Cheers, >>> >>> Miles >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Rhino Tools Dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
