public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] Git et al
Date: Wed, 29 Jan 2014 16:54:00 -0000	[thread overview]
Message-ID: <52E93243.8040106@users.sourceforge.net> (raw)
In-Reply-To: <20140129115302.GA11319@tastycake.net>

On 2014-01-29 05:53, Adam Dinwoodie wrote:
> I have an outstanding issue with the packaging I've just spotted --
> git-cvs relies on perl-DBD-SQLite, which doesn't exist.

More specifically, there has been one for x86_64 since I built 
git.x86_64 during the bootstrap, but I see now that I didn't add it for 
x86.  I just uploaded an x86 package.

But along these lines, git-email also needs a few Perl modules which are 
not yet available for x86; I'll proceed with those as well, hopefully 
tonight.

> 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?

I'm not sure to what debates you are referring, but the point of the 
split was to provide correct dependencies while isolating those to the 
components that actually need them.  This was already done with the more 
obvious tcl-tk dependency of gitk and git-gui, but my packages took it a 
step further.  So, for example, git-svn actually requires 
subversion-perl, but subversion is not small and not all git users are 
going to want that just in order to use git.


Yaakov

  reply	other threads:[~2014-01-29 16:54 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
2014-01-29 16:54           ` Yaakov (Cygwin/X) [this message]
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=52E93243.8040106@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --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).