public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Deleting old versions of packages
Date: Tue, 29 Oct 2013 20:50:00 -0000	[thread overview]
Message-ID: <20131029205038.GA392@ednor.casa.cgf.cx> (raw)
In-Reply-To: <87ppqnj15b.fsf@Rainer.invalid>

On Tue, Oct 29, 2013 at 09:02:56PM +0100, Achim Gratz wrote:
>Leave everything as is at the upload side, but add two cleanup passes on
>the release directory; a first that deletes zero-sized files and a
>second that removes empty directories.  That way a maintainer can
>"upload" a file that he wants to be deleted.  Then upset will see the
>cleaned up release directory and setup.ini won't have to specify tzhe
>exact versions of files most of the time.

I don't think I have to worry about empty directories.  Those are easy
to purge.  I was trying to avoid the zero-length file scenario but maybe
that's the best that can be done.  The ordering would have to be right
so that upset doesn't first reference a file and then delete it of
course.

In another discussion someone suggested a web-based form for deletion
but if I was going to use that, I might as well use that method for
upload too.  I don't think I'm ready to scrap sftp now that this is
implemented.

  reply	other threads:[~2013-10-29 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 22:31 New upload method: Deleting old versions David Stacey
2013-10-23  2:14 ` Christopher Faylor
2013-10-28 19:34   ` Deleting old versions of packages Christopher Faylor
2013-10-28 20:22     ` Achim Gratz
2013-10-29  0:03       ` Christopher Faylor
2013-10-29 20:03         ` Achim Gratz
2013-10-29 20:50           ` Christopher Faylor [this message]
2013-11-14 19:33             ` Christopher Faylor
2013-11-14 20:32               ` Achim Gratz
2013-11-14 20:45                 ` Christopher Faylor
2013-11-08 16:43     ` Damien Doligez

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=20131029205038.GA392@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --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).