On Thu, 18 Sep 2003 08:01:46 +0200
Matthias Urlichs <[EMAIL PROTECTED]> wrote:
> Hi,
>
> many packages seem to contain .orig.tar.gz files which may or may not
> be directly related to the files actually available from upstream.
> That is unfortunate.
>
> I think that it would make sense to add a
On Thu, 18 Sep 2003 02:01:25 -0500
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Pristine sources are already a desired, but not required,
> characteristic. There are enough brain dead upstream packaging
> practices that we can not mandate pristine sources.
Dont go blaming "upstream" for
On Mon, 16 Dec 2002 12:12:08 +0100
Wichert Akkerman <[EMAIL PROTECTED]> wrote:
> Previously Adam DiCarlo wrote:
> > Well, before I venture on this, is there a way we can store certain
> > data in control.tar.gz or something but without bloating the Packages
> > file?
>
> No.
Well, not with exist
Debian policy mentions a "version number" in a number of places. I think
it is misleading to call it a number, a version string would be more
precise.
Calling it a version number may give people the false impression that a
'.' is a decimal point rather than a seperator.
Also its a stretch to call
On Fri, 21 Sep 2001 03:35:33 +1000
Anthony Towns wrote:
> On Fri, Sep 21, 2001 at 02:28:47AM +1000, Glenn McGrath wrote:
> > The 'normal' component by itself should be called 'crippled'.
> > 'Crippled': A damaged or defective object or device.
>
The 'normal' component by itself should be called 'crippled'.
'Crippled': A damaged or defective object or device.
The 'non-US' component should be called 'enhance' (or something else).
'Enhance': To make greater, as in value, beauty, or effectiveness;
augment.
When both 'crippled' and 'enhance'
Remco Blaakmeer wrote:
>
> On Sun, 21 Jan 2001, Jakob Bøhm wrote:
>
> > Placing crypto software in any part of the main
> > archive still has a very important legal problem:
>
>
> > Sorry, to be putting down a nice idea, but I would
> > hate to see the project getting in trouble from
> > check
7 matches
Mail list logo
