Best place to update package changes

Oct 7, 2010 at 2:38 AM

I know we have package sources inside the codebase right now but just wondering about a go-forward basis. For example I got this request from @kkozmic (Castle maintainer)

"... please rename castle.ioc to castle.Windsor and put "Castle Project Contributors" as authors..."

So we can do this in the current codebase but what's our longer term plan on where the source for .nuspec content should be? In Nu, the creator of the Gem holds the info and we encourage them to either a) talk to the maintainer of the orginal project to get them to fold it into their own build process or b) be the Gem owner and just keep it up to date separately from the project code. I did this with Ayende and RavanDB for example, and just made him the owner of the gem so it works well as it's part of RavanDB build now.

Thoughts around longer term storage, short term updates, etc. for packages?

Oct 7, 2010 at 2:41 AM

Eventually, we'll have a real gallery.  For now, people can just send pull request on the http://nupackpackages.codeplex.com/ repo.  3 people already submitted packaged this way today.  But this is definitely a short term solution.

Oct 7, 2010 at 2:44 AM
4 people. :) I sent a pull request for ColorCode because Matt Hawley wants it as a dependency for WikiPlex.

From: davidebb [notifications@codeplex.com]
Sent: Wednesday, October 06, 2010 6:41 PM
To: Drew Miller
Subject: Re: Best place to update package changes [nupack:229901]

From: davidebb

Eventually, we'll have a real gallery. For now, people can just send pull request on the http://nupackpackages.codeplex.com/ repo. 3 people already submitted packaged this way today. But this is definitely a short term solution.

Oct 7, 2010 at 2:49 AM

I just did the suggested Windsor rename