public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] Git et al
Date: Wed, 29 Jan 2014 11:53:00 -0000	[thread overview]
Message-ID: <20140129115302.GA11319@tastycake.net> (raw)
In-Reply-To: <52E277DC.9050502@redhat.com>

On Fri, Jan 24, 2014 at 07:25:32AM -0700, Eric Blake wrote:
> On 01/15/2014 04:06 AM, Adam Dinwoodie wrote:
> > There's a new build available at http://tastycake.net/~adam/cygwin/
> > which resolves that issue.  If you want to give it a try and let me know
> > how you get on, I'd be exceedingly grateful.
>
> I've now had a chance to test this, and at least my use cases worked.  I
> can't say I used ALL of git functionality, but what I did use shows that
> your build is good.  Let's go ahead and pass the maintainer baton.

I have an outstanding issue with the packaging I've just spotted --
git-cvs relies on perl-DBD-SQLite, which doesn't exist.  I suspect this
is a result of taking Yaakov's cygport files.  I've not used Git's CVS
tools before, so it might take me a little while to work out whether the
problems I'm seeing are the result of missing packages, PEBCAK or
something else.

Thinking about it, my build and packages take Yaakov's work over at
Cygwin Ports to split the Git packages (at the moment, git-cvs is part
of the main git package, for example, while my build separates it out).
I know there have been debates about this in the past; is there
currently any guideline about the best way to manage such package
splits?

  reply	other threads:[~2014-01-29 11:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 20:02 Adam Dinwoodie
2014-01-11 20:04 ` Adam Dinwoodie
2014-01-13  9:25 ` Corinna Vinschen
2014-01-13 21:32 ` Eric Blake
2014-01-13 23:59   ` Adam Dinwoodie
2014-01-15 11:06     ` Adam Dinwoodie
2014-01-17 18:42       ` Balaji Venkataraman
2014-01-17 18:48         ` Christopher Faylor
2014-01-17 22:58           ` Balaji Venkataraman
2014-01-24 14:25       ` Eric Blake
2014-01-29 11:53         ` Adam Dinwoodie [this message]
2014-01-29 16:54           ` Yaakov (Cygwin/X)
2014-01-29 17:07             ` Adam Dinwoodie
2014-01-30 10:00               ` Yaakov (Cygwin/X)
2014-01-29 17:45             ` Achim Gratz
2014-01-29 19:33               ` Jan Nijtmans
2014-01-29 19:56                 ` Achim Gratz
2014-06-10 22:00 ` Yaakov Selkowitz
2014-06-10 22:36   ` Adam Dinwoodie
2014-06-11  3:55     ` Achim Gratz
2014-06-11  4:23       ` Achim Gratz
2014-06-11  4:20     ` Yaakov Selkowitz
2014-07-19  7:29       ` Adam Dinwoodie
2014-07-19 13:54         ` Christopher Faylor
2014-07-19 23:47         ` David Rothenberger
2014-07-21  7:46           ` Adam Dinwoodie
2014-08-04 21:41             ` Adam Dinwoodie
2014-08-13 19:12               ` Adam Dinwoodie
2014-08-13 19:37                 ` Eric Blake
2014-08-15  4:25                   ` Eric Blake
2014-08-15  4:46                     ` Marco Atzeri
2014-08-15  8:25                     ` Adam Dinwoodie
2014-08-15  8:31                       ` Adam Dinwoodie
2014-08-15  7:05                 ` Yaakov Selkowitz
2014-08-20 20:19                   ` Adam Dinwoodie
2014-08-20 22:19                     ` Yaakov Selkowitz
2014-08-18 18:38                 ` Eric Blake
2014-09-21 12:57                   ` Andrew Schulman

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=20140129115302.GA11319@tastycake.net \
    --to=adam@dinwoodie.org \
    --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).