FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 08-23-2011, 07:32 AM
Guido Günther
 
Default git-buildpackage could use get-orig-source, uscan ?

Hi Jérémy,
On Sun, Oct 25, 2009 at 12:12:09PM +0100, Jérémy Lal wrote:
> I noticed bzr-buildpackage is able to get upstream tarball
> with get-orig-source or uscan, if they exist.
> Should git-buildpackage (and others) provide the same feature ?

git-import-orig has --uscan.
-- Guido

>
> Regards,
> Jérémy Lal
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110823073245.GA10926@bogon.sigxcpu.org">http://lists.debian.org/20110823073245.GA10926@bogon.sigxcpu.org
 
Old 08-23-2011, 08:03 AM
Chow Loong Jin
 
Default git-buildpackage could use get-orig-source, uscan ?

On 23/08/2011 15:32, Guido Günther wrote:
> Hi Jérémy,
> On Sun, Oct 25, 2009 at 12:12:09PM +0100, Jérémy Lal wrote:
>> I noticed bzr-buildpackage is able to get upstream tarball
>> with get-orig-source or uscan, if they exist.
>> Should git-buildpackage (and others) provide the same feature ?
>
> git-import-orig has --uscan.

Maybe git import-orig should also get a --get-orig-source option.

--
Kind regards,
Loong Jin
 
Old 08-23-2011, 06:01 PM
Guido Günther
 
Default git-buildpackage could use get-orig-source, uscan ?

On Tue, Aug 23, 2011 at 04:03:19PM +0800, Chow Loong Jin wrote:
> On 23/08/2011 15:32, Guido Günther wrote:
> > Hi Jérémy,
> > On Sun, Oct 25, 2009 at 12:12:09PM +0100, Jérémy Lal wrote:
> >> I noticed bzr-buildpackage is able to get upstream tarball
> >> with get-orig-source or uscan, if they exist.
> >> Should git-buildpackage (and others) provide the same feature ?
> >
> > git-import-orig has --uscan.
>
> Maybe git import-orig should also get a --get-orig-source option.
is get-orig-source really a good interface? Wouldn't it make more sense
to fix uscan if needed?
Cheers,
-- Guido


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110823180119.GA19117@bogon.sigxcpu.org">http://lists.debian.org/20110823180119.GA19117@bogon.sigxcpu.org
 
Old 08-24-2011, 12:47 AM
Chow Loong Jin
 
Default git-buildpackage could use get-orig-source, uscan ?

On 24/08/2011 02:01, Guido Günther wrote:
> On Tue, Aug 23, 2011 at 04:03:19PM +0800, Chow Loong Jin wrote:
>> On 23/08/2011 15:32, Guido Günther wrote:
>>> Hi Jérémy,
>>> On Sun, Oct 25, 2009 at 12:12:09PM +0100, Jérémy Lal wrote:
>>>> I noticed bzr-buildpackage is able to get upstream tarball
>>>> with get-orig-source or uscan, if they exist.
>>>> Should git-buildpackage (and others) provide the same feature ?
>>>
>>> git-import-orig has --uscan.
>>
>> Maybe git import-orig should also get a --get-orig-source option.
> is get-orig-source really a good interface? Wouldn't it make more sense
> to fix uscan if needed?

Well sometimes you need to do special things to get a DFSG clean tarball.

On the other hand, I think many get-orig-source targets don't perform as
specified in [1]. More specifically, this part:
> This target may be invoked in any directory, and should take care to clean
> up any temporary files it may have left.

From past experiences, many get-orig-source targets can't be invoked outside of
the source directory, and even if they could, you'd have some debian/ directory
detection hackery looking like..
DEBIAN_DIR = $(dir $(firstword $(MAKEFILE_LIST))

which doesn't support paths with spaces in them. (who needs spaces in paths, eh?)

Some get-orig-source targets also prefer to get the current tarball, rather than
the latest tarball as mentioned in [1].

Perhaps uscan should be fixed to get a --script option to mangle tarballs after
downloading them. And possibly also to get VCS support for packages that don't
have upstream tarballs.

How does bzr buildpackage do it anyway?

[1] http://www.debian.org/doc/debian-policy/ch-source.html

--
Kind regards,
Loong Jin
 
Old 08-24-2011, 12:55 AM
Chow Loong Jin
 
Default git-buildpackage could use get-orig-source, uscan ?

On 24/08/2011 08:47, Chow Loong Jin wrote:
> On 24/08/2011 02:01, Guido Günther wrote:
>> On Tue, Aug 23, 2011 at 04:03:19PM +0800, Chow Loong Jin wrote:
>>> On 23/08/2011 15:32, Guido Günther wrote:
>>>> Hi Jérémy,
>>>> On Sun, Oct 25, 2009 at 12:12:09PM +0100, Jérémy Lal wrote:
>>>>> I noticed bzr-buildpackage is able to get upstream tarball
>>>>> with get-orig-source or uscan, if they exist.
>>>>> Should git-buildpackage (and others) provide the same feature ?
>>>>
>>>> git-import-orig has --uscan.
>>>
>>> Maybe git import-orig should also get a --get-orig-source option.
>> is get-orig-source really a good interface? Wouldn't it make more sense
>> to fix uscan if needed?
>
> Well sometimes you need to do special things to get a DFSG clean tarball.
>
> On the other hand, I think many get-orig-source targets don't perform as
> specified in [1]. More specifically, this part:
>> This target may be invoked in any directory, and should take care to clean
>> up any temporary files it may have left.
>
> From past experiences, many get-orig-source targets can't be invoked outside of
> the source directory, and even if they could, you'd have some debian/ directory
> detection hackery looking like..
> DEBIAN_DIR = $(dir $(firstword $(MAKEFILE_LIST))
>
> which doesn't support paths with spaces in them. (who needs spaces in paths, eh?)
>
> Some get-orig-source targets also prefer to get the current tarball, rather than
> the latest tarball as mentioned in [1].
>
> Perhaps uscan should be fixed to get a --script option to mangle tarballs after
> downloading them. And possibly also to get VCS support for packages that don't
> have upstream tarballs.
>
> How does bzr buildpackage do it anyway?
>
> [1] http://www.debian.org/doc/debian-policy/ch-source.html
>

http://wiki.debian.org/SandroTosi/Svn_get-orig-source is a perfect example of
what I just mentioned. It doesn't work outside of the source directory
(dpkg-pasrechangelog won't find a debian/changelog), and it creates an orig
tarball for the current revision (as parsed out of dpkg-parsechangelog) rather
than the new revision.

--
Kind regards,
Loong Jin
 
Old 08-26-2011, 06:33 PM
Guido Günther
 
Default git-buildpackage could use get-orig-source, uscan ?

On Wed, Aug 24, 2011 at 08:47:03AM +0800, Chow Loong Jin wrote:
> On 24/08/2011 02:01, Guido Günther wrote:
> > On Tue, Aug 23, 2011 at 04:03:19PM +0800, Chow Loong Jin wrote:
> >> On 23/08/2011 15:32, Guido Günther wrote:
> >>> Hi Jérémy,
> >>> On Sun, Oct 25, 2009 at 12:12:09PM +0100, Jérémy Lal wrote:
> >>>> I noticed bzr-buildpackage is able to get upstream tarball
> >>>> with get-orig-source or uscan, if they exist.
> >>>> Should git-buildpackage (and others) provide the same feature ?
> >>>
> >>> git-import-orig has --uscan.
> >>
> >> Maybe git import-orig should also get a --get-orig-source option.
> > is get-orig-source really a good interface? Wouldn't it make more sense
> > to fix uscan if needed?
>
> Well sometimes you need to do special things to get a DFSG clean tarball.
>
> On the other hand, I think many get-orig-source targets don't perform as
> specified in [1]. More specifically, this part:
> > This target may be invoked in any directory, and should take care to clean
> > up any temporary files it may have left.
>
> From past experiences, many get-orig-source targets can't be invoked outside of
> the source directory, and even if they could, you'd have some debian/ directory
> detection hackery looking like..
> DEBIAN_DIR = $(dir $(firstword $(MAKEFILE_LIST))

Most of this looks mostly useful when not importing the upstream tarball
into git. If you want to do cleanups you can do so after importing the
tarball using the help of git or you can add filters to git-import-orig
which then does the repack for you.
Cheers,
-- Guido

>
> which doesn't support paths with spaces in them. (who needs spaces in paths, eh?)
>
> Some get-orig-source targets also prefer to get the current tarball, rather than
> the latest tarball as mentioned in [1].
>
> Perhaps uscan should be fixed to get a --script option to mangle tarballs after
> downloading them. And possibly also to get VCS support for packages that don't
> have upstream tarballs.
>
> How does bzr buildpackage do it anyway?
>
> [1] http://www.debian.org/doc/debian-policy/ch-source.html
>
> --
> Kind regards,
> Loong Jin
>



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110826183316.GA28830@bogon.sigxcpu.org">http://lists.debian.org/20110826183316.GA28830@bogon.sigxcpu.org
 

Thread Tools




All times are GMT. The time now is 12:56 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org