public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: cygwin-apps@cygwin.com
Subject: Re: [Attn Maintainer] git git-svn
Date: Fri, 07 Aug 2015 20:50:00 -0000	[thread overview]
Message-ID: <20150807205024.GV14466@dinwoodie.org> (raw)
In-Reply-To: <877fpe19le.fsf@Rainer.invalid>

On Sun, Aug 02, 2015 at 08:35:25AM +0200, Achim Gratz wrote:
> The tests for 2.5.0 just completed:
> 
> --8<---------------cut here---------------start------------->8---
> fixed   1
> success 12528
> failed  0
> broken  179
> total   12808
> --8<---------------cut here---------------end--------------->8---
> 
> …on both architectures.  I do not have cvs installed, so those tests (as
> well as Perforce) have not run.

I'm going to continue to be cautious: while I think the risk of bumping
up to v2.5.0 is very low, if there are problems with that or any of the
other numerous recent changes (this has been the first time a release
has got above the -1 version since I took over maintainership), I want
to keep the changes reasonably slow to help narrow down where the
problem comes from.

> A few suggestions for changes to the cygport:
> 
> --8<---------------cut here---------------start------------->8---
> SRC_URI="https://git.kernel.org/cgit/git/git.git/snapshot/${PN}-v${PV}.tar.gz"
> SRC_DIR="${PN}-v${PV}"
> --8<---------------cut here---------------end--------------->8---
> 
> Then not "inherit git", a snapshot is less wasteful then the cloning
> unless you plan to really work with the repository which cygport makes
> difficult anyway.

Done.  I switched from something similar when I took over the
maintainership, as using "inherit git" seemed like The Right Thing To Do
when I was first playing around with Cygport.  As you say, though, it's
just adding overhead with no advantage.  (Indeed if I want to play
around with the Git repository itself, I already have a copy of that
ready to go.)


> --8<---------------cut here---------------start------------->8---
> [[ $ARCH_x86_64 ]] && DEPEND="$DEPEND libiconv libiconv-devel"
> --8<---------------cut here---------------end--------------->8---
> 
> Drop this line and add libiconv, libiconv-devel plus dblatex to the
> DEPENDS unconditionally.

I'm sure when I first added that line, it made sense with the
dependencies.  I've made this change as well now, though, as it seems to
be the right thing to do at this point.

Thanks!

Adam

  reply	other threads:[~2015-08-07 20:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 19:45 Achim Gratz
2015-07-27 21:30 ` Adam Dinwoodie
2015-07-28  5:44   ` Achim Gratz
2015-07-30  1:01     ` Adam Dinwoodie
2015-07-30 19:41       ` Achim Gratz
2015-08-01 14:18         ` Jon TURNEY
2015-08-01 15:26           ` Adam Dinwoodie
2015-08-01 18:18             ` Achim Gratz
2015-08-07 20:46               ` Adam Dinwoodie
2015-08-02  6:35       ` Achim Gratz
2015-08-07 20:50         ` Adam Dinwoodie [this message]
2015-08-08  5:38           ` Achim Gratz

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=20150807205024.GV14466@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=Stromeko@nexgo.de \
    --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).