public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: [RFU] lftp
Date: Tue, 28 May 2013 18:06:00 -0000	[thread overview]
Message-ID: <ags9q81jcdidjv77dmmsi36p1rpftoja7o@4ax.com> (raw)
In-Reply-To: <20130528102144.GC5264@calimero.vinschen.de>

> On May 28 05:27, Andrew Schulman wrote:
> > > On 2013-05-27 15:46, Andrew Schulman wrote:
> > > > wget \
> > > >   http://home.comcast.net/~andrex2/cygwin/lftp/lftp-4.4.7-1.tar.bz2 \
> > > >   http://home.comcast.net/~andrex2/cygwin/lftp/lftp-4.4.7-1-src.tar.bz2 \
> > > >   http://home.comcast.net/~andrex2/cygwin/lftp/lftp-debuginfo-4.4.7-1.tar.bz2
> > > 
> > > Uploaded, and removed 4.4.0-1.
> > > 
> > > But in the future, please use the cygport-generated structure for your 
> > > uploads and add the necessary flags to wget (e.g. -r -nH --cut-dirs=2), 
> > > so that lftp-debuginfo is a subdirectory of lftp as it should be.  That 
> > > will make it much easier to upload in the future.
> > 
> > I'm happy to oblige, and I see that lftp-debuginfo is in its own directory in
> > the mirrors.  But what you see above is how cygport is creating the files - all
> > together in the same directory as my .cygport file.  So this is the first I've
> > heard of it.
> > 
> > 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.

Thanks,
Andrew.

  parent reply	other threads:[~2013-05-28 18:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 20:44 Andrew Schulman
2013-05-27 20:46 ` Andrew Schulman
2013-05-28  6:05   ` Yaakov (Cygwin/X)
2013-05-28  9:28     ` Andrew Schulman
2013-05-28 10:21       ` Corinna Vinschen
2013-05-28 12:56         ` marco atzeri
2013-05-28 18:06         ` Andrew Schulman [this message]
2013-05-28 19:01           ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2013-08-10 18:27 Schulman, Andrew
2013-08-10 21:12 ` Ken Brown
2013-03-03 15:40 Andrew Schulman
2013-03-03 17:26 ` Christopher Faylor
2013-03-03 23:40 ` Chris Sutcliffe
2013-03-04  3:58   ` Yaakov
2013-03-04 18:38   ` Christopher Faylor
2013-03-04 21:23     ` Andrew Schulman
2013-03-04 21:28       ` Christopher Faylor
2012-10-04  1:34 Andrew Schulman
2012-10-05  1:38 ` Christopher Faylor
2012-05-31 18:53 Andrew Schulman
2012-05-31 19:29 ` Andrew Schulman
2012-06-01 10:18   ` Corinna Vinschen
2012-04-17 18:12 Andrew Schulman
2012-04-17 18:49 ` Yaakov (Cygwin/X)
2012-04-17 21:02   ` Andrew Schulman
2011-05-03 14:21 Andrew Schulman
2011-05-03 14:25 ` Corinna Vinschen
2011-04-26 14:02 Andrew Schulman
2011-04-26 15:48 ` Corinna Vinschen
2010-10-21 19:50 Andrew Schulman
2010-10-21 23:10 ` Yaakov (Cygwin/X)
2010-10-22 13:53   ` Andrew Schulman
2010-10-22 17:14     ` Yaakov (Cygwin/X)
2010-10-22 14:07   ` Andrew Schulman
2010-10-22 14:40     ` Christopher Faylor
2010-01-07 15:18 Andrew Schulman
2010-01-07 17:11 ` Andrew Schulman
2010-01-07 17:43   ` Corinna Vinschen
2010-01-07 17:53     ` Andrew Schulman
2010-01-07 18:08       ` Corinna Vinschen
2009-01-21 20:29 Andrew Schulman
2009-01-22  9:00 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ags9q81jcdidjv77dmmsi36p1rpftoja7o@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).