From: "Paul G." <pgarceau@qwest.net>
To: cygwin@cygwin.com
Subject: Re: setup test #4
Date: Sun, 04 Nov 2001 15:58:00 -0000 [thread overview]
Message-ID: <3BE565B2.9471.891080@localhost> (raw)
In-Reply-To: <1004687949.6899.2.camel@lifelesswks>
On 2 Nov 2001 at 18:59, the Illustrious Robert Collins wrote:
> On Fri, 2001-11-02 at 18:45, Paul G. wrote:
> >
> >
> > On 2 Nov 2001 at 17:52, the Illustrious Robert Collins wrote:
> >
> > > On Fri, 2001-11-02 at 17:37, Paul G. wrote:
> > > > snapshot -4
> > >
> > > > Does "Keep" care whether binary has been installed or not? If
> > > > not, then "Keep+src=ticked" would handle this nicely.
> > >
> > > Yes, keep is for the case where a package is installed.
> > > Additionally, there is no uninstall for source currently!
> >
> > Ok.
> >
> > Think I found another bug, one that could be changed in to a
> > "feature" ;-).
> >
> > It is assumed that you have already downloaded the binary using
> > setup.exe -4.
> >
> > When uninstalling a binary package, such as patch, from setup.exe,
> > the logical result is that the patch binary is removed.
> >
> > You can then, using snapshot -4, download the source by selecting
> > revision 0.0 and setting "src=ticked". Interesting. The
> > funny/interesting thing is that if you have the binary installed,
> > revision 0.0 does not appear ;-). Revision 0.0 only appears after an
> > uninstall of the binary package has occurred, or at least so it would
> > seem.
>
> Which package? I just tried this cron, and while it did default to
> "source" rather the current version - something I'm about to fix :} - it
> wouldn't show 0.0 for me. 0.0 is show for packages that don't have a
> version stamp - and some of the old packages don't or didn't have
> versions. You may have 'lucked' onto one of those in the 'prev' field.
I was looking at Utils category when I discovered this. patch and time both show this
behaviour. time is always set to version 0.0. patch is reverted to version 0.0.
Sounds like I did "luck" in to it...;-).
Anyway, thought it was interesting. Haven't taken time to look through all categories.
Database category does not have this behaviour, at least not with postgresql.
Paul G.
>
> Rob
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next parent reply other threads:[~2001-11-04 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BE1DE91.3862.B9D979@localhost>
[not found] ` <1004687949.6899.2.camel@lifelesswks>
2001-11-04 15:58 ` Paul G. [this message]
2001-11-04 17:44 Robert Collins
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=3BE565B2.9471.891080@localhost \
--to=pgarceau@qwest.net \
--cc=cygwin@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).