From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org, Axel Beckert <abe@deuxchevaux.org>
Subject: Re: Zsh on Debian is beginning to rot
Date: Mon, 10 Sep 2012 07:59:36 -0700 [thread overview]
Message-ID: <504E0058.8010802@eastlink.ca> (raw)
In-Reply-To: <20120910001601.GW30122@sym.noone.org>
On 09/09/12 05:16 PM, Axel Beckert wrote:
> Hi Mark,
>
> On Sun, Sep 09, 2012 at 08:38:08PM +0200, Mark van Dijk wrote:
>>> Squeeze is about 1.5 years old, Squeeze's feature freeze was in the
>>> beginning of August 2010 and zsh 4.3.10 was the uptodate zsh
>>> developement (!) release back then.
>> Yeah, so it's 2 years old and it did have some minor fixes since then.
>> The word 'rot' was chosen poorly sorry about that, if I pissed you
>> off too much I apologise.
> Ah, civility triumphs.
>
>
>
> Gentlemen, this brings up a meta question of mine that I can't find the
> answer too anywhere. It's off topic, but since we have a genuine Debian
> packager at hand, maybe he can answer it, or perhaps point me to some
> doc that does explain it.
>
>
>
> Why are Debian packages often so far behind?--vs, say, Arch, who often
> have packages out the day after they are released from upstream? This
> is not a bitchy comment, it is an honest question--I'm sure there is a
> very good reason, I'd just like to know what it is. What is involved in
> making a package? I'd have thought that when someone releases
> something, it would take five minutes to just 'wrap it up' into the
> package format and that would be that. When I download something as SRC
> and build it, it often seems 'that simple', yet packaging things seems
> to be quite a chore and to take years.
>
>
>
> Take Xfce. I'd like to try 4.10. Now, I know I can build it from SRC,
> but why is it that (at least last time I checked) it is not available in
> Testing? Arch had a package of it out, literally a couple of days
> after it was released. What is it that Debian packagers do that takes
> so long? I get the feeling that somehow software packages need to be
> customized and tweaked for a year or two before they can be included.
> Why? Slackware makes it a point of pride that they don't customize or
> tweak stuff at all, and yet, they too seem to take their time getting
> packages together, and they release a monolithic distro like Debian as
> if (so it might seem) all the parts have to be carefully checked out and
> mated to all the other parts to avoid disaster. OTOH, Arch seems to
> feel that you can put things together any way you want and it should all
> work like lego. It should all work like lego.
>
>
>
> Or take the current thing, Debian/zsh. It sounds like Axel has put his
> heart and soul into Debian/zsh, but what on Earth does that involve?
> I'd have thought that zsh is zsh is zsh regardless of the distro. If
> anyone can help me to get a ground level understanding of this whole
> subject I'd be very obliged.
next prev parent reply other threads:[~2012-09-10 15:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 11:10 Mark van Dijk
2012-09-09 11:48 ` Frank Terbeck
2012-09-10 8:06 ` Vincent Lefevre
2012-09-10 8:42 ` Frank Terbeck
2012-09-10 12:13 ` Vincent Lefevre
2012-09-10 8:56 ` Michael Prokop
2012-09-10 11:59 ` Vincent Lefevre
2012-09-10 13:11 ` Axel Beckert
2012-09-09 17:51 ` Axel Beckert
2012-09-09 18:38 ` Mark van Dijk
2012-09-10 0:16 ` Axel Beckert
2012-09-10 14:59 ` Ray Andrews [this message]
2012-09-10 18:42 ` Axel Beckert
2012-09-11 0:15 ` Vincent Lefevre
2012-09-11 11:45 ` zsh-beta vs zsh Debian package (was: Re: Zsh on Debian [...]) Axel Beckert
2012-09-12 0:40 ` Clint Adams
2012-09-12 11:41 ` Vincent Lefevre
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=504E0058.8010802@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=abe@deuxchevaux.org \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).