public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: 116145@bugs.debian.org To: gcc-gnats@gcc.gnu.org Subject: libgcj/7854: fastjar update (-u) should be implemented Date: Sun, 08 Sep 2002 00:36:00 -0000 [thread overview] Message-ID: <20020908072747.641.qmail@sources.redhat.com> (raw) >Number: 7854 >Category: libgcj >Synopsis: fastjar update (-u) should be implemented >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Sun Sep 08 00:36:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: 116145@bugs.debian.org >Release: 3.2 / HEAD >Organization: >Environment: >Description: [known, but not in GNATS yet, see http://bugs.debian.org/116145] fastjar's -u option is disabled due to corrupted archives. Per Bothner responded: Yes, I ran into the same problem. Basically the implementation of 'u' is pretty much not there. I looked at trying to fix it, but decided I didn't have time. Until somebody fixes it, we should change fastjar to exit with an error on 'u'. The first question is whether fastjar should try to update in place or create a temporary file and copy it over. The former is faster, especially when just adding files, and is less liable to run out of disk space. However, it is tricky when files are replaced that are not at the end. In that case I guess the solution is to read the archive members that need to be moved into main memory. Then it is just a small matter of programming ... >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-09-08 7:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020908072747.641.qmail@sources.redhat.com \ --to=116145@bugs.debian.org \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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).