public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Yaakov S <yselkowitz@netscape.net> To: cygwin-xfree@cygwin.com Subject: Heads-up: xfig uninstall Date: Thu, 01 Jan 2004 19:34:00 -0000 [thread overview] Message-ID: <bt1soi$vlc$1@sea.gmane.org> (raw) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Something I came across regarding the xfig package: xfig-base requires xfig-lib and xfig-lib requires xfig-base. Sounds at first like it make sense, but it leads to a very interesting problem: this makes it very difficult to uninstall. Actually it reminds me of an old arcade game, where a head would pop up in one place, and when you go to hit it, it would appear somewhere else, ~ etc. If xfig-base and xfig-lib are both installed (which due to their inter-dependency they would be) and you first select one to uninstall. When you go to choose the other for uninstall, first you must click-thru Reinstall (Keep, Reinstall, Uninstall ...) which then triggers the first to Keep. You can go back and forth like this for a while until you feel like you're playing that game again. I did find one work-around by accident, although I forgot exactly how I did it. It involves an interrupted (un)install of one of the two, followed by another run of setup.exe which can then uninstall both. I'm sure xfig is a nice package, but I don't see a need for anyone to be stuck with it. :-) Anyway, I hope this helps. Yaakov Selkowitz Cygwin 'd' maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQE/9HZRpiWmPGlmQSMRAnhFAKDFoNabvD93suOlKT+oftIqn/QGFQCglNdi okb+3xbiRBrK/ki2C1amKgs= =7EX8 -----END PGP SIGNATURE-----
next reply other threads:[~2004-01-01 19:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-01 19:34 Yaakov S [this message] 2004-01-02 5:56 ` Harold L Hunt II
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='bt1soi$vlc$1@sea.gmane.org' \ --to=yselkowitz@netscape.net \ --cc=cygwin-xfree@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: 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).