RE: [cdt-dev] rpm plugins

[Sebastien Marineau <sebastien@xxxxxxx>]

Hi Jeremy,

Doug is right on this. There are a couple of ways to do this, but one
is to create a project and commit group for this; the second way is to
create a project/commiter group for contributions in general (or maybe just
Linux extensions), and roll your plugins under that (and in the future 
possibly have others).

The first question, though, is whether everyone agrees that this fits under
the CDT mandate, as opposed to "plugin central" or sourceforge. I guess
I'm looking for a concensus from the group here, as this is a departure from
the generic frameworks/plugins approach we have taken up to now.

If we get agreement to go forward with this, the next step is to send this
to
John for his approval.

Thanks,

Sebastien

> -----Original Message-----
> From: Douglas Schaefer [mailto:dschaefe@xxxxxxxxxx]
> Sent: Thursday, June 17, 2004 4:03 PM
> To: cdt-dev@xxxxxxxxxxx
> Cc: cdt-dev@xxxxxxxxxxx; cdt-dev-admin@xxxxxxxxxxx; Jeremy Handcock
> Subject: Re: [cdt-dev] rpm plugins
> 
> 
> Hey Jeremy,
> 
> The mechanics of such an arrangement should be pretty simple. 
> We already 
> have (well, 'had' actually, but we'll address that shortly) 
> the CPPUnit 
> integration hosted on eclipse.org. We would have create a new 
> commit group 
> that would allow access to the source and just setup the rest 
> of CVS and 
> bugzilla accordingly.
> 
> This would require the approval of the Project Lead (Sebastien), and 
> likely the Tools PMC (John Duimovich). I'm not sure where 
> Sebastien is 
> with this but the ball would start there.
> 
> Doug Schaefer, IBM's Eclipse CDT Architect
> Ottawa (Palladium), Ontario, Canada
> 
> 
> 
> Jeremy Handcock <handcock@xxxxxxxxxx> 
> Sent by: cdt-dev-admin@xxxxxxxxxxx
> 06/17/2004 03:10 PM
> Please respond to
> cdt-dev
> 
> 
> To
> cdt-dev@xxxxxxxxxxx
> cc
> Jeremy Handcock <handcock@xxxxxxxxxx>
> Subject
> Re: [cdt-dev] rpm plugins
> 
> 
> 
> 
> 
> 
> On Thu, Jun 17, 2004 at 10:31:32AM -0400, Alain Magloire wrote:
> > We could do like the JDT/platform, they provide extra tools in the
> > repository ex:
> > 
> platform-core-home/downloads/tools/org.eclipse.core.tools.rest
> orer_1.0.0.zip
> > platform-core-home/downloads/tools/org.eclipse.core.tools_1.0.0.zip
> > 
> > so maybe: cdt-home/downloads/tools/...
> 
> Rather than a binary-only distribution, we would really like 
> to see the
> RPM and Oprofile plug-in sources hosted as a part of (or 
> alongside) the
> CDT on eclipse.org, where all development would be done in the open.
> I'd like to open up some discussion on how we can achieve this.
> 
> > But I would suggest the tools be package in zip not in rpms
> 
> Yes, of course.  Zip files would be distributed in the same fashion as
> the CDT itself.
> 
> Jeremy
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>