[Pkg-gauche-devel] gauche multiarch support

[NIIBE Yutaka]

I updated all Gauche related packages of mine to be team maintained.
Feel free to upload by yourselves.

Speaking about packaging...

On 2013-01-21 at 13:24 +0100, Jens Thiele wrote:
> NIIBE Yutaka <gniibe at fsij.org> writes:
> 
> > Besides, I am considering how Debian package should be maintained,
> > say, for forthcoming 0.9, given the situation that upstream use Git
> > and have the repositories.
> >
> > Having the standard repository of git-buildpackage (with pristine-tar,
> > etc.) would be one way.  But, it would be overkill.
> >
> > It seems for me that, if we use Git to maintain Debian package and
> > upstream, we don't need to stick "released source code distribution"
> > which includes generated configure scripts.  It would be OK that
> > Debian's "source code" for Gauche doesn't include generated configure
> > scripts, but those will be generated at build time.
> >
> > I think:
> > It is no problem for Debian packaging, even if it doesn't maintain all
> > information by upstream (released source code tar ball and released
> > generated configure scripts), but just maintain the Git repository of
> > upstream.
> >
> > How do you think?
> 
> I am not sure about that one / don't really know. AFAIR to build the git
> version you already need gauche? where the release tarballs are
> buildable without gauche? In general I would prefer to stay as close to
> upstream as possible.

I don't care much about bootstrapping.  We maintain Debian package, and
we have Gauche already.

My concern is how to maintain Debian packages for Gauche. 

There are many ways to maintain Debian packaging.  If we don't use
Git, it's basically getting released tar ball and adding the 'debian/'
directory.  Some packages use Git for Debian packaging independently
(not related to upstream Git repository), they have their own
repository, for full source code, or only debian/ things.  Some
packages use git-buildpackage for their maintenance and their
repositories have all: upstream source code, released tar balls
information, as well as debian specific things.

Given the situation that upstream has Git repository, if we don't care
about the release process of upstream (of generating files), it will
become simpler when we have Git repository of our Debian packaging
with our own 'debian' branch which has 'debian/' directory, and not
have any released tar balls information.  You know, many files are
anyway generated by the build process on Debian because Debian has
it's own config{.sub,.guess} or we touch configure.ac, etc.

No, I haven't tested any for Git only Debian build for Gauche.  I just
wrote my ideas.
--