On Wed, Sep 21, 2011 at 12:31 AM, Troy Howard <thowar...@gmail.com> wrote:

> While it may be a bit redundant, why couldn't there be an individual
> package for each piece of contrib and a "Lucene.Net Contrib (All)"
> package that drags them all down.
>
> That way users can grab just the bit they need, or if they just want
> to get the whole thing, grab the "All" package.
>
> Thanks,
> Troy
>


That was the idea for the Lucene.Net-Essentials & Lucene.Net-Full packages.

"We can also create additional higher level packages which have dependencies
on the other ones.   Possibly a Lucene.Net-Essentials and Lucene.Net-Full."



>
>
> On Tue, Sep 20, 2011 at 9:11 PM, Aaron Powell <m...@aaron-powell.com> wrote:
> > I'm going to vote +1 for granular.
> >
> > With the RC you could look at myget and have a Lucene.Net repository on
> there so people can go for unstable on myget, stables on nuget.
> >
> > Also, I came across this article which explains how to setup a build
> server to automatically push to nuget/ myget which could be useful to the
> maintainers:
> http://brendanforster.com/doing-the-build-server-dance-with-nuget.html
> >
> > Aaron Powell
> > MVP - Internet Explorer (Development) | FunnelWeb Team Member
> >
> > http://apowell.me | http://twitter.com/slace | Skype: aaron.l.powell |
> Github | BitBucket
> >
> > -----Original Message-----
> > From: Prescott Nasser [mailto:geobmx...@hotmail.com]
> > Sent: Wednesday, 21 September 2011 2:05 PM
> > To: lucene-net-dev@lucene.apache.org
> > Subject: RE: [Lucene.Net] Nuget, Lucene.Net, and Your Thoughts
> >
> >
> >> Right now there are two packages: Lucene & Lucene.Contrib. My question
> >> to the community is do you wish to finer grain packages, i.e. a
> >> package for each contrib project or continue to keep it simple.
> >>
> >
> >
> > +1 Granular, we just need to be good about descriptions.
> >
> >
> >>
> >> Another topic to converse about is would you like to see an
> >> out-of-band project nuget feed for nightly builds, branches with new
> >> or experimental features, or stable code snapshots for a projected
> release?
> >
> >
> > Having a package for the latest RC would probably be a good idea
> >
>

Reply via email to