[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Dropins refactoring

Thanks!

On Tue, 2013-07-30 at 13:55 +0200, Pascal Rapicault wrote:
> I started working on an answer to your questions earlier this morning.
> With the other things I have to do, I'm hoping to be done with this by 
> tomorrow.
> 
> On 07/30/2013 01:02 PM, Krzysztof Daniel wrote:
> > Hey,
> >
> > any chance to get an answer?
> >
> > On Fri, 2013-07-05 at 13:12 +0200, Krzysztof Daniel wrote:
> >> Pascal, Ian,
> >>
> >> I've spent recently quite a lot of time trying to get installable repos
> >> installed as droplets.
> >>
> >> The problem that I will inevitably face is the conflict and ordering
> >> between dropins and droplets, and possibly other mechanisms, like
> >> profile dropping, etc.
> >>
> >> I was thinking about refactoring dropins to have:
> >> (a) central service for processing startup installation changes
> >> (b) service definition for installation changing services
> >> (c) implementation of dropins service.
> >>
> >> a. would be responsible for getting a request,  repositories, caching
> >> them and executing  request/plans
> >> c. would scan the dropins folder, produce a request and pass it to a.
> >>
> >> The point is that I'd like to avoid multiple refreshes of framework and
> >> solve in some way obvious startup conflicts (what is first? dropins or
> >> droplets?).
> >>
> >> Do you think something like this could make into official p2?
> >>
> > Best regards,
> 
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev


-- 
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
Red Hat