public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [patch] xfsprogs build tweaks for Debian
Date: Wed, 23 Sep 2009 10:08:54 +1000 (EST)	[thread overview]
Message-ID: <241547128.01253664531434.JavaMail.root@mail-au.aconex.com> (raw)
In-Reply-To: <20090922115707.GA8143@infradead.org>

----- "Christoph Hellwig" <hch@infradead.org> wrote:

> The tarball generated by Makepks does not contain .git.  Do you
> create a tarball in a different way for debian?

Building directly from a git tree - its a one-step process.

> 
> would be cleaner as
> 
> #
> # If we're on a Debian or Debian-derived system generate deb packages
> by
> # default, else RPM packages.
> #
> if [ -f /etc/debian_version ]
>     type=debian
> else
>     type=rpm
> fi

OK, yep, will do.

> Note that when you bump package version please always also tag the
> result in git.

Will do (and pull in & document those other merged changes when I do).

> > +	- Debian packaging updates, esp. readline6 dependency.
> 
> Btw, didn't readline move to GPLv3 while we have GPLv2 code in libxfs?

Hmm, not sure, will have to look into that.  The (new) dependency doesn't
specify any particular version, it just allows versions other than 5 ...
but still worth checking into.

thanks!

-- 
Nathan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2009-09-23  0:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <777659823.265181253164106522.JavaMail.root@mail-au.aconex.com>
2009-09-17 23:08 ` [patch] xfsprogs build tweaks for Debian Nathan Scott
2009-09-22 11:57   ` Christoph Hellwig
2009-09-22 12:15     ` Christoph Hellwig
2009-09-23  0:08     ` Nathan Scott [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=241547128.01253664531434.JavaMail.root@mail-au.aconex.com \
    --to=nscott@aconex.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.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