From: Sebastian Kuzminsky <seb@highlab.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, "H. Peter Anvin" <hpa@zytor.com>,
git@vger.kernel.org
Subject: Re: git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug)
Date: Mon, 31 Oct 2005 13:39:52 -0700 [thread overview]
Message-ID: <E1EWgRc-0003ME-Rg@highlab.com> (raw)
In-Reply-To: <46a038f90510311213n565010d6g5586a7484b25da7e@mail.gmail.com>
Martin Langhoff <martin.langhoff@gmail.com> wrote:
> On 11/1/05, Junio C Hamano <junkio@cox.net> wrote:
> > I am currently generating i386 RPMs and i386 debs myself but I
> > am not particularly proud of the current setup. I do not have
> > an RPM based machine that I can install the result myself to
> > test (which is what started this thread). Since I am not a
> > Debian developer (and I do not particularly wish to become one
> > myself), the debs I generate will not be official anyway.
> > Personally I'd be happier if I can just lose rpm and deb targets
> > from the "upstream" Makefile (git-core.spec file and debian/
> > subdirectory as well while we are at it), ask "packaging
> > maintainers" to pull from kernel.org/ tree and do RPMs and Debs
> > outside.
>
> I'd say you can probably keep the current setup, and as distro
> (format?) specific maintainers show up and start maintaining bits and
> pieces, merge from them. git should make that easy ;-)
>
> I'm not a DD -- but I'm on the 'NM queue' which means I'm in the
> process of turning into one (delayed at the moment, but hapenning
> soonish). Have a package in the archive, and a few sponsors who are
> generally happy to upload my work. Would be happy to give it a go if
> noone else steps up.
>
> (Sebastian _did_ indicate interest, and fought a long, hard battle in
> debian-devel about the naming of the git and cg utilities. I haven't
> seen him around lately (last post:
> http://marc.theaimsgroup.com/?l=3Dgit&m=3D112747921603277&w=3D2 ). May be
> on holiday? CC'd)
I'm here :-)
The GNU Interactive Tools people are changing their name (to "gitfm"),
but they want a script called "git" to remind people that the name
has changed... So I still have to rename our git to "gt" or something,
until they remove their git script.
We're going to use update-alternatives so people who dont care about
GNU Interactive Tools can call their git "git". This is in violation
of Debian Policy, but I'm hoping my sponsor will forgive me, as it is
just a temporary violation.
I hope to get this work done sometime this week, and if I have anything
useful I'll send the patches to the list.
--
Sebastian Kuzminsky
next prev parent reply other threads:[~2005-10-31 20:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 20:12 git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug) H. Peter Anvin
2005-10-30 20:40 ` Wolfgang Denk
2005-10-30 20:51 ` H. Peter Anvin
2005-10-30 22:16 ` Junio C Hamano
2005-10-30 22:37 ` [PATCH] Do not try installing SVNimport on RPM Junio C Hamano
[not found] ` <43654F4B.30103@zytor.com>
2005-10-30 23:39 ` Junio C Hamano
2005-10-30 22:28 ` git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug) Ryan Anderson
2005-10-30 23:01 ` Junio C Hamano
2005-10-31 5:44 ` Junio C Hamano
2005-10-31 6:41 ` Chris Wright
2005-10-31 6:48 ` Junio C Hamano
2005-10-31 15:57 ` H. Peter Anvin
2005-10-31 16:25 ` Linus Torvalds
2005-10-31 16:27 ` H. Peter Anvin
2005-11-01 23:11 ` Horst von Brand
2005-10-31 19:31 ` Junio C Hamano
2005-10-31 19:36 ` H. Peter Anvin
2005-10-31 20:13 ` Martin Langhoff
2005-10-31 20:32 ` Linus Torvalds
2005-10-31 20:44 ` Martin Langhoff
2005-10-31 20:46 ` H. Peter Anvin
2005-10-31 21:31 ` David Lang
2005-10-31 20:39 ` Sebastian Kuzminsky [this message]
2005-10-31 21:27 ` Junio C Hamano
2005-11-05 11:19 ` Package split: Debian Junio C Hamano
2005-11-01 23:15 ` git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug) Horst von Brand
2005-11-02 3:36 ` Junio C Hamano
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=E1EWgRc-0003ME-Rg@highlab.com \
--to=seb@highlab.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=junkio@cox.net \
--cc=martin.langhoff@gmail.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 NNTP newsgroup(s).