Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization

From: James Blackburn <jamesblackburn@xxxxxxxxx>
Date: Thu, 5 Aug 2010 18:43:11 +0100
Delivered-to: cdt-dev@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=xTGGs/1v8WSdD0gy5DJSjyZQP/m42ssU7iWihVY2gvdBkk0HDsUarfC8gMw7dUaYn0 78UDBNh+4r+tMizzgvCNZZue3GRNFcKMgo+cHf6JBFHLfHzcfmGnIB9UQYo5NmA4mbPN xmVKXJ1gkp6Y2fXLW9DqXRHhuSHvpmL6InfLE=
List-archive: <https://dev.eclipse.org/mailman/private/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>

On 5 August 2010 18:32, Andrew Overholt <overholt@xxxxxxxxxx> wrote:

> Sounds like a good discussion to have on p2-dev. I do know Red Hat has
> similar requirements in their distro,

Yup, and we currently use dropins just like James does.

Pascal has said dropins are deprecated (no user feedback when things go wrong, not the p2 way, etc.). Given dropins uses p2 API to reconcile the changes into the configuration, I know that everything I want to do is possible using the p2 API. There's just a functionality gap between what the p2 IApplications expose to admins and what would be required to support shared installs. I guess given that dropins have worked so far, its quite a neat straightforward back door into p2.

James

References:
- RE: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Marc Khouzam
- Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Tim Black
- Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Tim Black
- Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Tim Black
- RE: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Marc Khouzam
- RE: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: John Cortell
- RE: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: John Cortell
- Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Doug Schaefer
- Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: James Blackburn
- Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Doug Schaefer
- Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
  - From: Andrew Overholt

Prev by Date: Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
Next by Date: RE: [cdt-dev] move to line?
Previous by thread: Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
Next by thread: Re: [cdt-dev] best practices for managing a custom eclipse/CDT build in a C++ development organization
Index(es):
- Date
- Thread

Breadcrumbs