public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: lzma tarball usage
Date: Thu, 08 May 2008 22:21:25 +0300	[thread overview]
Message-ID: <1210274485.26658.10.camel@localhost> (raw)
In-Reply-To: <20080508190907.GL16108@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

On N, 2008-05-08 at 21:09 +0200, Fabian Groffen wrote:
> > e) It has been suggested the support should have been added with new
> > EAPI instead of local build deps (some of which are missing, for
> > instance in the hand-rolled for-no-reason-whatsoever .tar.lzma format
> > net-tools doesn't have a dep in addition to using lzma for no good
> > reason)
> 
> Chill, relax and cool down.

Well, I said how it is. I don't see anything in it that indicates I am
so upset and angry that I need to do these things. I did however loose
hours of work time, but that's life.

> Instead, just ask those who decided to
> follow upstream why and if they have even thought about the issues you
> brought up.

This is what I am doing with this as well, in addition to the bug
reports. But as this is widespread to at least 4-6 system packages, I
brought it up here as well to ensure this is not something I have to
fight against in overlays and time wastes continuously in the future.
Oh and net-tools has not distributed anything in .tar.lzma, so this has
nothing to do with following upstream in any shape or form in this case.

-- 
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-05-08 19:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 13:23 [gentoo-dev] RFC: lzma tarball usage Mart Raudsepp
2008-05-07 13:34 ` Fabian Groffen
2008-05-08 18:45   ` Mart Raudsepp
2008-05-08 19:09     ` Fabian Groffen
2008-05-08 19:17       ` Santiago M. Mola
2008-05-08 19:21       ` Mart Raudsepp [this message]
2008-05-17 15:55     ` Enrico Weigelt
2008-05-10  7:32   ` Mike Frysinger
2008-05-10  7:36     ` Fabian Groffen
2008-05-10  9:57       ` Mike Frysinger
2008-05-07 14:12 ` Natanael Copa
2008-05-07 14:55   ` Ulrich Mueller
2008-05-08  8:06     ` [gentoo-dev] " Duncan
2008-05-08 10:49       ` Diego 'Flameeyes' Pettenò
2008-05-08 10:59         ` Graham Murray
2008-05-08 11:31           ` Diego 'Flameeyes' Pettenò
2008-05-08 11:41         ` Ulrich Mueller
2008-05-07 14:53 ` [gentoo-dev] " Benedikt Morbach
2008-05-07 15:03   ` Ulrich Mueller
2008-05-07 15:02 ` Benedikt Morbach
2008-05-07 16:06 ` Chris Gianelloni
2008-05-07 18:38 ` Enrico Weigelt
2008-05-07 20:01   ` Richard Freeman
2008-05-07 20:10     ` Doug Goldstein
2008-05-08  0:52 ` [gentoo-dev] " Ryan Hill
2008-05-08 13:17   ` Doug Goldstein
2008-05-08 13:28     ` Ciaran McCreesh
2008-05-08 13:32       ` Doug Goldstein
2008-05-08 13:36         ` Ciaran McCreesh
2008-05-08 13:43           ` Doug Goldstein
2008-05-09  8:37             ` James Cloos
2008-05-08 14:30           ` Diego 'Flameeyes' Pettenò
2008-05-08 13:41         ` Doug Goldstein
2008-05-08 14:33           ` Robert Buchholz
2008-05-09  1:04     ` Ryan Hill
2008-05-08 11:30 ` [gentoo-dev] " Luca Barbato

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=1210274485.26658.10.camel@localhost \
    --to=leio@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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