This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [RFU] lftp
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 28 May 2013 21:01:49 +0200
- Subject: Re: [RFU] lftp
- References: <fah7q8llc3bvqoc91gohgkf2p62b99qgvi at 4ax dot com> <7gh7q8ts46j2qla9d8k6pdc0hhpfra4pmj at 4ax dot com> <7gh7q8ts46j2qla9d8k6pdc0hhpfra4pmj-e09XROE/p8c at public dot gmane dot org> <51A4490A dot 2010500 at users dot sourceforge dot net> <det8q8hnnpujc35rrke6pcm3g3fguc5frr at 4ax dot com> <det8q8hnnpujc35rrke6pcm3g3fguc5frr-e09XROE/p8c at public dot gmane dot org> <20130528102144 dot GC5264 at calimero dot vinschen dot de> <ags9q81jcdidjv77dmmsi36p1rpftoja7o at 4ax dot com>
- Reply-to: cygwin-apps at cygwin dot com
On May 28 14:06, Andrew Schulman wrote:
> > On May 28 05:27, Andrew Schulman wrote:
> > > If cygport is supposed to be putting lftp-debuginfo into its own directory, I'm
> > > not sure why it isn't.
> >
> > It is ;)
> >
> > Ignore the created toplevel files, rather cd into the cygport project
> > dir and then into the "dist" subdir. There you will find a proper
> > package directory, neatly arranged for upload, including all setup.hint
> > files.
>
> Hm, what do you know.
>
> > Yaakov, I'm wondering if it isn't time to do two things:
> >
> > - Create a new cygport version which does not create the toplevel
> > files anymore.
>
> Yes, that will force those of us who haven't been following to notice that
> something has changed. Expect of course a slew of "why won't cygport build my
> packages any more" messages, and then we'll all know what to do again.
>
> > - Create a short documentation how to create the new cygport files.
>
> Yes please. I keep reading bits and pieces about how things we used to have to
> do aren't required any more, but if it's not in the docs, it's too hard to go
> back and find.
Just as a sidenote, you could have a look into Yaakov's or my 64 bit
package cygport files. Of my packages see, for instance, gawk, openssh
and, FWIW, the cygwin package itself. The only thing you really have to
keep in mind is to specify the cygport file always with the .cygport
suffix:
$ cygport foo almostall # Wrong
$ cygport foo.cygport almostall # Correct
Btw., did you notice http://cygwin.com/ml/cygwin/2013-05/msg00379.html ?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat