Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-26 Thread Vladimir Gorr
On 5/25/06, Oliver Deakin <[EMAIL PROTECTED]> wrote: Vladimir Gorr wrote: > On 5/25/06, Oliver Deakin <[EMAIL PROTECTED]> wrote: >> >> Geir Magnusson Jr wrote: >> > Some stuff that got lost (because I got consumed by J1 and I was the >> > only one pushing on it) was the idea of ensuring that >>

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Oliver Deakin
Geir Magnusson Jr wrote: Vladimir Gorr wrote: whether does it mean the HDK will contain the sources (src.zip?) as well? Otherwise I don't understand what can be modified. Could you please clarify this? I know you addressed to oliver, but let me take a wack at it to see if I grok everyt

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Oliver Deakin
Vladimir Gorr wrote: On 5/25/06, Oliver Deakin <[EMAIL PROTECTED]> wrote: Geir Magnusson Jr wrote: > Some stuff that got lost (because I got consumed by J1 and I was the > only one pushing on it) was the idea of ensuring that > > 1) the HDK could be anywhere - the was no hard-wired spot. That

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Geir Magnusson Jr
Vladimir Gorr wrote: whether does it mean the HDK will contain the sources (src.zip?) as well? Otherwise I don't understand what can be modified. Could you please clarify this? I know you addressed to oliver, but let me take a wack at it to see if I grok everything One of the many mo

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Geir Magnusson Jr
Alexey Petrenko wrote: 2006/5/25, Oliver Deakin <[EMAIL PROTECTED]>: I imagine that an HDK would come in a zip format, much like the current snapshots [2]. I also suggest to add build date into zip name and internal directory name. Something like HDK_20060525/deploy and so on... Yes, I assu

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Geir Magnusson Jr
Oliver Deakin wrote: Geir Magnusson Jr wrote: Some stuff that got lost (because I got consumed by J1 and I was the only one pushing on it) was the idea of ensuring that 1) the HDK could be anywhere - the was no hard-wired spot. That allowed having multiple simultaneous HDKs (ex different s

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Vladimir Gorr
On 5/25/06, Oliver Deakin <[EMAIL PROTECTED]> wrote: Geir Magnusson Jr wrote: > Some stuff that got lost (because I got consumed by J1 and I was the > only one pushing on it) was the idea of ensuring that > > 1) the HDK could be anywhere - the was no hard-wired spot. That > allowed having multi

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Alexey Petrenko
2006/5/25, Oliver Deakin <[EMAIL PROTECTED]>: I imagine that an HDK would come in a zip format, much like the current snapshots [2]. I also suggest to add build date into zip name and internal directory name. Something like HDK_20060525/deploy and so on... It will let us keep few copies of HDK

Re: Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-25 Thread Oliver Deakin
Geir Magnusson Jr wrote: Some stuff that got lost (because I got consumed by J1 and I was the only one pushing on it) was the idea of ensuring that 1) the HDK could be anywhere - the was no hard-wired spot. That allowed having multiple simultaneous HDKs (ex different snapshot version) at the

Multi-tree HDK config - working directory ( was Re: Supporting working on a single module?)

2006-05-23 Thread Geir Magnusson Jr
Some stuff that got lost (because I got consumed by J1 and I was the only one pushing on it) was the idea of ensuring that 1) the HDK could be anywhere - the was no hard-wired spot. That allowed having multiple simultaneous HDKs (ex different snapshot version) at the same time as a full build