linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: Bruno Cornec <bruno@project-builder.org>,
	linux-mtd@lists.infradead.org, twebb <taliaferro62@gmail.com>,
	David.Woodhouse@intel.com
Subject: Re: latest MTD-utils
Date: Tue, 21 Sep 2010 17:27:32 +0300	[thread overview]
Message-ID: <1285079252.7512.136.camel@localhost> (raw)
In-Reply-To: <87sk131977.fsf@macbook.be.48ers.dk>

On Tue, 2010-09-21 at 16:07 +0200, Peter Korsgaard wrote:
> >>>>> "Artem" == Artem Bityutskiy <dedekind1@gmail.com> writes:
> 
> Hi,
> 
>  Artem> Peter, why would not you make a make tarball target, BTW? Sorry,
>  Artem> may be you explained, but I forgot.
> 
> You mean why don't I just checkout from git and make a tarball myself?
> 
> Tarballs are pretty much the standard for source releases, and
> source-based metadistributions (like Buildroot that I maintain) normally
> are optimized for tarballs rather than semi-random git snapshots
> (E.G. mirroring, automatic handling, ..).
> 
> And then there's the issue about people checking the ftp and not
> noticing that there's actually a new stable release out instead of the
> old 1.3.1

It is not too difficult to provide tarball, but this is something
developers do not care about, they develop. Packagers do care, and it is
saner when packagers do this, not developers.

I was in LinuxCon Brazil this year, and there was this presentation:
http://events.linuxfoundation.org/2010/linuxcon-brazil/cornec

where bruno said exactly the same. And he was promoting his project
which claims to be able to pick sources from anywhere - git, svn,
whatever.

So the question is, why Buildroot cannot adjust to the reality (which is
that developers in average do not care about tarballs) and cannot be
improved?

I'm not competent in the packaging area, though. Just a logical thought.
Also CCed Bruno, may he'll be interested to know his presentation was
listened to :-) Bruno, the beginning of the conversation is here:
http://lists.infradead.org/pipermail/linux-mtd/2010-September/032164.html

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2010-09-21 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 22:47 latest MTD-utils twebb
2010-09-21  7:25 ` Artem Bityutskiy
2010-09-21 13:45   ` Peter Korsgaard
2010-09-21 13:51     ` Artem Bityutskiy
2010-09-21 13:54       ` Artem Bityutskiy
2010-09-21 14:07         ` Peter Korsgaard
2010-09-21 14:27           ` Artem Bityutskiy [this message]
2010-09-21 14:42             ` Peter Korsgaard
2010-09-23 12:03               ` Artem Bityutskiy
2010-09-23 12:13                 ` Peter Korsgaard
2010-09-22 22:47             ` Bruno Cornec
2010-09-21 15:24       ` David Woodhouse
2010-09-21 14:03     ` twebb

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=1285079252.7512.136.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=David.Woodhouse@intel.com \
    --cc=bruno@project-builder.org \
    --cc=jacmet@sunsite.dk \
    --cc=linux-mtd@lists.infradead.org \
    --cc=taliaferro62@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).