From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Deleting old versions of packages
Date: Mon, 28 Oct 2013 19:34:00 -0000 [thread overview]
Message-ID: <20131028193452.GA5968@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20131023021452.GC8111@ednor.casa.cgf.cx>
On Tue, Oct 22, 2013 at 10:14:52PM -0400, Christopher Faylor wrote:
>On Tue, Oct 22, 2013 at 11:31:34PM +0100, David Stacey wrote:
>>Thanks to CGF for the effort that has gone into the new upload process -
>>I've just uploaded a new package called 'icoutils' and it was really
>>quite painless.
>>
>>One thing I haven't grasped yet is the mechanism by which old versions
>>are deleted. If I were to upload a new version of an existing package,
>>how would I go about removing the oldest?
>
>Eventually old packages will be deleted (actually archived) automatically.
>I haven't yet added that functionality to upset though. Maybe this weekend
>if I have the time.
The problem with this method is that it forces you to use a setup.hint
file to delete packages. For instance, I just had a case where I wanted
make-4.0-2 to be curr and make-3.82.90-1 to be prev. I really don't
want to have to change setup.hint to enforce that because that's error
prone. If that's exactly what people were trying to warn me about then
I apologize for being dense.
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.
cgf
next prev parent reply other threads:[~2013-10-28 19:34 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 ` Christopher Faylor [this message]
2013-10-28 20:22 ` Deleting old versions of packages Achim Gratz
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=20131028193452.GA5968@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).