cygport: Adding arbitrary files to the src package

Christopher Faylor
Mon May 7 20:52:00 GMT 2012

On Mon, May 07, 2012 at 04:40:56PM -0400, Christopher Faylor wrote:
>On Mon, May 07, 2012 at 10:01:44PM +0200, Corinna Vinschen wrote:
>>On May  7 15:44, Christopher Faylor wrote:
>>> On Mon, May 07, 2012 at 09:33:57PM +0200, Corinna Vinschen wrote:
>>> >On May  7 20:09, marco atzeri wrote:
>>> >> On 5/7/2012 5:06 PM, Corinna Vinschen wrote:
>>> >> >### FIXME:
>>> >> >   ###
>>> >> >   ### Where to put the cygwin1.dbg file so that it ends up "as is" in the
>>> >> >   ### source tarball?
>>> >> 
>>> >> why not in a dedicate cygwin-debug package ?
>>> >> Having it in
>>> >> 
>>> >> /usr/bin/cygwin1.dbg
>>> >> 
>>> >> will simplify debugging, instead of having it in the source package
>>> >> and manually extract and copying in /usr/bin
>>> >
>>> >Any chance you have a hidden camera installed in my office?  That's
>>> >how I actually implemented it in my cygport file (and what I meant when
>>> >I wrote "There are other ways to handle the file").
>>> >
>>> >I was trying to find a way to keep it as part of the source archive,
>>> >just as it has been so far, though.
>>> FWIW, I think it makes sense for it to be a separate package or even for
>>> it just to be installed along-side cygwin1.dll in the standard
>>> distribution.  We already install /usr/include along with cygwin1.dll so
>>> it sorta kinda is consistent to also include cygwin1.dbg too if you
>>> squint at it just right.
>>That's a good point.  I think I'd prefer the extra cygwin-debug package,
>>but we could even go a step further and create a cygwin-devel package
>>instead, which contains the contents of /usr/include, /usr/lib, and
>>asorted files from usr/bin like, say, cygwin1.dbg, dumper.exe, ssp.exe,
>>strace.exe.  That's dead simple with cygport. 
>I think a cygwin-devel makes sense but I wasn't going to suggest the
>extra work.
>How fine-grained do we get though?  cygwin-support for cygcheck.exe and
>mount.exe?  cygwin-devel for /usr/include?  cygwin-debug for cygwin1.dbg?
>The advantages, of course, are that we *could* decouple release of
>cygwin-* from the "main" cygwin1.dll package if we really wanted to.

(with the exception of cygwin-debug)


More information about the Cygwin-apps mailing list