Bas Wijnen <[EMAIL PROTECTED]> wrote:
> Also, someone noted that this script is vulnerable to a symlink attack in
> /tmp. I haven't found a good solution for that though, because I want to have
> a reachable build tree under a "normal" name, where I can see what all the
> files look like.
If you
Interesting thread. I've never thought about generating the tarball this
way, though I do have a lot of native packages that probably shouldn't
be.
If one general-purpose tool to handle this rises to the top and is
usable by many people, it would be a good candidate for addition to
devscripts.
--
also sprach Ben Finney <[EMAIL PROTECTED]> [2006.09.07.0803 +0200]:
> Unfortunately, Debian doesn't yet have a 'bzr-buildpackage' package.
James (and I) are working on it:
http://wiki.debian.org/BzrBuildpackage
--
Please do not send copies of list mail to me; I read the list!
.''`. martin
also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.09.07.0714 +0200]:
> That's what I do for releases as well. For normal testing builds though
> (that's to see if the package builds and works without planning a release),
> creating a tarball and unpacking it first is too much work IMO. So I wrote
Hi Ben,
if you create yourself the orig.tar.gz, the building tools from debian
don't try to create it themselves.
i.e. something like:
tar cvzf foo_X.Y.orig.tar.gz --exclude=foo-X.Y/debian foo-X.Y
before actually building the package should solve your problem.
Hope this helps, Eric
--
You don't
On Thursday 07 September 2006 09:42, Russ Allbery wrote:
> Bas Wijnen <[EMAIL PROTECTED]> writes:
> > That's what I do for releases as well. For normal testing builds though
> > (that's to see if the package builds and works without planning a
> > release), creating a tarball and unpacking it firs
Bas Wijnen <[EMAIL PROTECTED]> writes:
> That's what I do for releases as well. For normal testing builds though
> (that's to see if the package builds and works without planning a
> release), creating a tarball and unpacking it first is too much work
> IMO. So I wrote a script to do these thing
On Thu, Sep 07, 2006 at 02:03:28PM +1000, Ben Finney wrote:
> So that leads to the question: What "best practices" are there for
> creating the Debian sources ('foo_X.Y.orig.tar.gz', 'foo_X.Y-Z.dsc',
> 'foo_X.Y-Z.diff.gz') automatically from a source working tree that
> already contains the 'debian
"Roberto C. Sanchez" <[EMAIL PROTECTED]> writes:
> On Thu, Sep 07, 2006 at 02:03:28PM +1000, Ben Finney wrote:
> > I've seen many recommendations that the 'debian/' directory should not
> > be part of the 'foo_X.Y.orig.tar.gz' tarball but should always be
> > added by the 'foo_X.Y-Z.diff.gz', even
On Thursday 07 September 2006 08:14, Bas Wijnen wrote:
> On Wed, Sep 06, 2006 at 09:48:42PM -0700, Russ Allbery wrote:
> > Ben Finney <[EMAIL PROTECTED]> writes:
> > > I've seen many recommendations that the 'debian/' directory should not
> > > be part of the 'foo_X.Y.orig.tar.gz' tarball but shoul
On Thu, Sep 07, 2006 at 02:03:28PM +1000, Ben Finney wrote:
> Howdy all,
>
> I've seen many recommendations that the 'debian/' directory should not
> be part of the 'foo_X.Y.orig.tar.gz' tarball but should always be
> added by the 'foo_X.Y-Z.diff.gz', even in the case of "I *am* the
> upstream and
On Wed, Sep 06, 2006 at 09:48:42PM -0700, Russ Allbery wrote:
> Ben Finney <[EMAIL PROTECTED]> writes:
>
> > I've seen many recommendations that the 'debian/' directory should not
> > be part of the 'foo_X.Y.orig.tar.gz' tarball but should always be added
> > by the 'foo_X.Y-Z.diff.gz', even in th
Ben Finney <[EMAIL PROTECTED]> writes:
> I've seen many recommendations that the 'debian/' directory should not
> be part of the 'foo_X.Y.orig.tar.gz' tarball but should always be added
> by the 'foo_X.Y-Z.diff.gz', even in the case of "I *am* the upstream and
> I prefer to track the 'debian/' dir
13 matches
Mail list logo
