List:Internals« Previous MessageNext Message »
From:MARK CALLAGHAN Date:June 16 2009 9:39pm
Subject:Re: RFC: draft of physical structure of server code
View as plain text  
On Tue, Jun 16, 2009 at 12:26 PM, Mats Kindahl<mats@stripped> wrote:
> Hi Mark,
>
> Thank you for your comments. I will try to answer your questions below.
>
> MARK CALLAGHAN wrote:
>> What is the first step?
>
> Seeing if there are any problems with this approach of a package structure.
>
> Once this is set, we enable a number of other worklogs (see WL#4737 for rough
> list of refactoring issues).
>
> W.r.t. the physical structure, the next steps are:
>
> 1. Fixing header files (WL#4877)
>
> 2. Providing a unified build frame (WL#4875)
>
> 3. Identifying candidate packages turn them into packages.

Sounds good. There will be a little pain for people (like me) who need
to update their patches during this transition. But we will be much
better off when this gets done.

-- 
Mark Callaghan
mdcallag@stripped
Thread
RFC: draft of physical structure of server codeMats Kindahl11 Jun
  • Re: RFC: draft of physical structure of server codeKonstantin Osipov16 Jun
    • Re: RFC: draft of physical structure of server codeMats Kindahl16 Jun
  • Re: RFC: draft of physical structure of server codeMARK CALLAGHAN16 Jun
    • Re: RFC: draft of physical structure of server codeMats Kindahl16 Jun
      • Re: RFC: draft of physical structure of server codeMARK CALLAGHAN16 Jun