Bug#899073: [uscan][RFC] please support something like uscan components for multiple tar.gz

[Chris Lamb]

Bastien,

> Ping ?

(Please note that I am not a devscripts/uscan maintainer.)

> > The amount of code to be reviewed remains constant, merely that the number
> > of source packages is far fewer from a statistics point of view.
> >
> > The number of line of code to review will increase but the number of
> > package under 1ko will decrease

I'm not really convinced this would save any time, let alone saving
enough to warrant the ugly code bundling and possibly dangerous quasi-
embedded code copies.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#899073: [uscan][RFC] please support something like uscan components for multiple tar.gz

[Bastien ROUCARIES]

On Sat, May 19, 2018 at 10:49 PM, Bastien ROUCARIES
 wrote:
> On Fri, May 18, 2018 at 10:50 PM, Chris Lamb  wrote:
>> severity 899073 wishlist
>> tags 899073 + moreinfo
>> thanks
>>
>> [Tagging +moreinfo due to RFC status & "wishlist" as it's a feature request]
>>
>> Hi Bastien,
>>
>>> For packaging a lot of too small node package we will like that uscan 
>>> support
>>> to download from multiple source with different version ala uscan component.
>>
>> If I understand this correctly, you plan to ship similar/related node
>> packages as separate components of a single source package.
>
> Yes like node-tap that ship (using manual uscan) one line source code
> package own-or and own-or-env, or node-function bind that ship one
> liner node-has
>
>>
>>> It will decrease the load of small pacakge for us and decrease the load of
>>> ftpmasters
>>
>> If so, could you clarify exactly how this would help ftpmaster? The
>> amount of code to be reviewed remains constant, merely that the number
>> of source packages is far fewer from a statistics point of view.
>
> The number of line of code to review will increase but the number of
> package under 1ko will decrease. And i think it is easier for you to
> review
> a tar.gz decompressed, than to reviewing copyright of patches (usually
> small package are added with the help of patch). That why I said, it
> will simplify your work.
>
>> Indeed, it might even be additional work for all as, for example,
>> problem with (eg.) component 14 out of 27 might would delay the entire
>> thing and cause confusion about exactly which package one is referring
>> to at any point in time.
>
> I understand, but it will reserved to only really small package like
> the node-is-odd that sit in the NEWS queue (that could be I think
> rejected) . This kind of package could be merge with the rdepend with
> no loss of generality.
>
> We could not get upstream to be (censured), but we could try something
> on your side.

Ping ?
>
> Bastien
>
>>
>> Best wishes,
>>
>> --
>>   ,''`.
>>  : :'  : Chris Lamb
>>  `. `'`  la...@debian.org / chris-lamb.co.uk
>>`-

Bug#899073: [uscan][RFC] please support something like uscan components for multiple tar.gz

[Bastien ROUCARIES]

On Fri, May 18, 2018 at 10:50 PM, Chris Lamb  wrote:
> severity 899073 wishlist
> tags 899073 + moreinfo
> thanks
>
> [Tagging +moreinfo due to RFC status & "wishlist" as it's a feature request]
>
> Hi Bastien,
>
>> For packaging a lot of too small node package we will like that uscan support
>> to download from multiple source with different version ala uscan component.
>
> If I understand this correctly, you plan to ship similar/related node
> packages as separate components of a single source package.

Yes like node-tap that ship (using manual uscan) one line source code
package own-or and own-or-env, or node-function bind that ship one
liner node-has

>
>> It will decrease the load of small pacakge for us and decrease the load of
>> ftpmasters
>
> If so, could you clarify exactly how this would help ftpmaster? The
> amount of code to be reviewed remains constant, merely that the number
> of source packages is far fewer from a statistics point of view.

The number of line of code to review will increase but the number of
package under 1ko will decrease. And i think it is easier for you to
review
a tar.gz decompressed, than to reviewing copyright of patches (usually
small package are added with the help of patch). That why I said, it
will simplify your work.

> Indeed, it might even be additional work for all as, for example,
> problem with (eg.) component 14 out of 27 might would delay the entire
> thing and cause confusion about exactly which package one is referring
> to at any point in time.

I understand, but it will reserved to only really small package like
the node-is-odd that sit in the NEWS queue (that could be I think
rejected) . This kind of package could be merge with the rdepend with
no loss of generality.

We could not get upstream to be (censured), but we could try something
on your side.

Bastien

>
> Best wishes,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

Bug#899073: [uscan][RFC] please support something like uscan components for multiple tar.gz

[Chris Lamb]

severity 899073 wishlist
tags 899073 + moreinfo
thanks

[Tagging +moreinfo due to RFC status & "wishlist" as it's a feature request]

Hi Bastien,

> For packaging a lot of too small node package we will like that uscan support 
> to download from multiple source with different version ala uscan component.
 
If I understand this correctly, you plan to ship similar/related node
packages as separate components of a single source package.

> It will decrease the load of small pacakge for us and decrease the load of 
> ftpmasters

If so, could you clarify exactly how this would help ftpmaster? The
amount of code to be reviewed remains constant, merely that the number
of source packages is far fewer from a statistics point of view.

Indeed, it might even be additional work for all as, for example, a
problem with (eg.) component 14 out of 27 might would delay the entire
thing and cause confusion about exactly which package one is referring
to at any point in time.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#899073: [uscan][RFC] please support something like uscan components for multiple tar.gz

[Bastien ROUCARIÈS]

Package: devscripts
Version: 2.18.2
Severity: important
X-Debbugs-CC: pkg-javascript-de...@lists.alioth.debian.org
X-Debbugs-CC: ftpmas...@debian.org

Hi,

For packaging a lot of too small node package we will like that uscan support 
to download from multiple source with different version ala uscan component.

It will decrease the load of small pacakge for us and decrease the load of 
ftpmasters (here in cc) and allow to package automatically like I have done 
manualy for node-function-bind.

uscan main (foo package) will be still debian/watch and every package will 
need to create a watch file under debian/component-name/watch and a version 
file under
debian/component-name/VERSION

However, it will be nice to contrary to uscan component it will be nice that 
uscan save every component under foo.orig-component-VERSION.tar.gz

Ideally it will not need to modify tracker and pts

Thank you

signature.asc
Description: This is a digitally signed message part.