[opencoe-developer] Fwd: Re: SourceForge ID

[Ron B. <ron...@ya...>]

 
> I just registered a sourceforge ID recently. 
...
> I have used your COESDK segment. I have following
> question: The standard directory name of DII COE
> software development kit is DII_DEV, why are you
> used COESDK as directory name. I browsed your code
> of COESDK segment. I found that the first line of
> TestInstall is "#!/usr/bin/perl -I /h/dii_dev/lib",
> but others used "#!/usr/bin/perl -I/h/COESDK/lib".
> Why the directory name is inconsistent?
> 
> 

The COESDK is probably the most unready COE segment.
My original intentions was to create a toolkit that
would create segments packages that could be installed
by the official DII COE Installer. But without a
sample of their "validation" algorithm, that is not
possible.

I changed the pathing from dii_dev to COESDK for two
reasons. 1) Consistency since the SDK is an actual
segment, I felt I should use the PREFIX for the path
and 2) Inter-operability - I thought I might get the
opportunity to run the DIIDEV and COESDK tools side by
side and wanted to deconflict their pathh names.

COE Segmentation is problematic. Is it better to use
the COE 3.X rules? Native formats (MSI, RPM, PKG)?
Other cross-platform packaging (OpenPKG, IzPack)? I
have not really finished thinking about the design of
this.
 
--

Sorry I have been off line for a few weeks. A small
vacation, much work, and an unfortunate scripting
error which destroyed my entire development
directories (thank god for backups which recovered
most of my recent work) have slowed my reply.

Thank you for your continuing interest. I will email
you privately when I enroll you as a project member.

--ron


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com