git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Stepan Kasal <kasal@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: spec file in tarball (was: Eliminate curl binary)
Date: Tue, 03 Jun 2008 09:08:28 -0700 (PDT)	[thread overview]
Message-ID: <m3ve0qzekl.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080603152054.GA19027@camelia.ucw.cz>

Stepan Kasal <kasal@ucw.cz> writes:

> On Tue, Jun 03, 2008 at 07:23:21AM -0700, Jakub Narebski wrote:
> > Stepan Kasal <kasal@ucw.cz> writes:
> > >
> > > [...], I do think that including Fedora-style spec files and
> > > other distribution-specific files into the tarball is a mistake.

<whine>But I use it...</whine>

> > Not only Fedora (and Fedora derivatives) use RPMs.
> 
> I always suspected this is just a wish, I had the impression that
> the rpm-based distribution has diverged too much.
> 
> > Besides, git.spec generated by git Makefile from git.spec.in
> > isn't distribution specific.
> 
> I often hear this, yet I see e.g. SuSE or Polish Linux creating spec
> files very different from what is used in Fedora.

True, spec files for a given _distribution_ (SuSE, PLD, Mandriva)
are often _distribution specific_, containing bits that make distro
different (for example translations of summary and description).

That doesn't change the fact, that git.spec file generated during
build system and contained in the tarball (it is _single file_!),
and RPM files in http://www.kernel.org/pub/software/scm/git/RPMS/
are (I think) not distribution specific, and can be installed on
[almost] any RPM-based distribution.

> > And it allows me to install git
> > in a packaging system on and old machine with old Aurox 11.1
> > (Polish distribution, no longer active, based on Fedora Core 4),
> > with glibc-2.3.5-10.3 via "rpmbuild --rebuild" from .src.rpm.
> 
> (I suppose you meant "rpmbuild -ta", that's the feature which takes
> the spec file from the tarball.)

No, I meant "rpmbuild --rebuild git-*.src.rpm", which I download
from kernel.org. I could use "rpmbuild -ta git-*.tar.gz" instead,
but I'm just used to this way of installing/upgrading git on my
machine.

> The value of this statement is limited by the fact that it's a fork
> of Fedora.  What value does that spec file bring for Mandrake users,
> for example?

Besides I think that git.git git.spec.in file is a good basis for
distribution specific spec files...

-- 
Jakub Narebski
Poland
ShadeHawk on #git

      reply	other threads:[~2008-06-03 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 10:53 Eliminate curl binary Stepan Kasal
2008-06-03 11:14 ` Johan Herland
2008-06-03 12:13   ` Stepan Kasal
2008-06-03 13:58     ` Stepan Kasal
2008-06-03 14:23       ` Jakub Narebski
2008-06-03 15:20         ` spec file in tarball (was: Eliminate curl binary) Stepan Kasal
2008-06-03 16:08           ` Jakub Narebski [this message]

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=m3ve0qzekl.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kasal@ucw.cz \
    /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 NNTP newsgroup(s).