public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Deleting old versions of packages
Date: Mon, 28 Oct 2013 20:22:00 -0000	[thread overview]
Message-ID: <87ppqpqh7m.fsf@Rainer.invalid> (raw)
In-Reply-To: <20131028193452.GA5968@ednor.casa.cgf.cx> (Christopher Faylor's	message of "Mon, 28 Oct 2013 15:34:52 -0400")

Christopher Faylor writes:
> I don't like the clunkiness of creating anti-files in the sftp directory
> to force deletions but I can't think of any other way to do this short
> of actually making it look like the entire release directory is in the
> user's sftp area.

What we've got is what I'd call a transactional procedure for
maintaining our packages.  The positive part is implemented: if the
transaction gets committed (!ready) then any files get transferred to
the release directory.

Removing files is difficult for two reasons: a) we don't easily know the
current state of the release directory and b) setup.hint may allow
multiple states depending on what is already in the release directory.

Keeping the deletion part a manual operation is possible, but probably
goes against your intentions and a !delete file is iffy.  So my proposal
would be that the current state of the release directory is mirrored
with (zero-sized?) files in the sftp area.  A maintainer could then just
delete any of those placeholders and the corresponding file would be
deleted from the release directory.  Crucially, the upload and the
deletion would not necessarily need to happen with the same transaction.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

  reply	other threads:[~2013-10-28 20:22 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 [this message]
2013-10-29  0:03       ` Christopher Faylor
2013-10-29 20:03         ` Achim Gratz
2013-10-29 20:50           ` Christopher Faylor
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=87ppqpqh7m.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).