Hi

at 12.11.2010 05:11, KP Kirchdoerfer wrote:
> The code is up to date in cvs, maybe you just try again or you give some more 
> information on the error you see.

I can always start from scratch , which I did yesterday, Just that it
takes more than 3 hours to just build the buildenv. I have not startet
the complete build, I am afraid it will take a very long time.

For me it is just difficult to understand why there is no way to neither
update buildenv nor the sources. It takes too much effort to keep up.

I have not dug in too deep into buildtool and its CVS interface, I was
doint too much perl in the past and don't really like its syntax.
I am wondering if we could not let 'make' solve the dependencies in the
source tree. I do not understand how buildtool decides that it has
nothing to do. I _believe_ it just consults conf/installed but does not
dig deeper and looks if there ave been updates to a package.

The 'make' command does a lot better in this context.

Could we document a way where we download and maintain a working copy of
the whole source tree and add a dependency to that tree to the makefiles
instead of a dependency to a local copy in the source. That way an
update command would immediately lead to a rebuild of a single
program/package.

I believe I found what I am looking for, it might have been clear to the
inner circle, but then....

Changing the Server tag in conf/sources.cfg allows to use either a local
copy or a 'real' CVS repository.

I will test this and see

cheers

Erich

------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to