[ITP] cygport

Yaakov S (Cygwin Ports) yselkowitz@users.sourceforge.net
Fri May 5 22:33:00 GMT 2006

Jason Alonso wrote:
> Perhaps it would be slightly more elegant to put the cygclass files in
> $prefix/share/cygport and export all of the functions defined in the
> cygport script itself into tidy .sh files in $prefix/lib/cygport/lib? 
> I'm not strongly advocating these particular paths, but I kinda feel
> like the *.cygport files are misplaced and that the cygport script
> itself could be modularized one step farther.

I'm not sure why /usr/share/cygport is less misplaced than 
/usr/lib/cygport/lib, except that the former sounds more accessible than 
the latter.  Either way, cygport still needs to be documented, then it 
shouldn't really matter where the components are actually installed.

Regarding further modularization, remember that for every script 
executed, you have another bash process running or you need to inherit a 
cygclass; therefore, the most common tasks are in cygport itself, to 
avoid excessive inherit commands or runtime overhead.

And there are certain things that _cannot_ be modularized, e.g. insinto, 
which exports a variable needed by doins, can't be separate because 
AFAIK you can only export variables to child processes and not to the 
parent/sibling processes.

In the end, nothing is finalized, and cygport should be flexible enough 
to move certain things into or out of /usr/lib/cygport/bin without 
changing API.


More information about the Cygwin-apps mailing list