From: Maarten De Boer <mdeboer@iua.upf.es>
To: linux-audio-dev@music.columbia.edu
Cc: alsa-devel@lists.sourceforge.net, debian-powerpc@lists.debian.org
Subject: Re: [linux-audio-dev] Poll: Distro for audio and MIDI development
Date: Wed, 23 Jul 2003 22:28:09 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.44.0307232212360.29546-100000@iua-mail.upf.es> (raw)
In-Reply-To: <3F1EC6D2.5010600@sambara.org>
This is a nice coincidence, because I just installed Debian Sid
('unstable') on my home workstation.
I am also a convinced Debian user, and all the servers and workstations
I administrate are Debian Woody ('stable'). Now, recently, I have seen
myself forced to install more and more backported packages, and backporting
some myself, because Debian stable is rather conservative, and this can be
a problem if you have new hardware, esp. video cards, or if you need to run
recent versions of applications, are depend on recent versions of
libraries...
Personally, I think the release cycle of Debian should be a lot shorter,
and I think a lot of people agree with that. On the other hand, on the
web/mail/file/cvs servers I run, I really want stable. The good thing is,
you get the choice, and I think Debian is the only distro with such a
choice. A lot of distro's present unstable and untested things as
stable. For me the clearest example, and actually the reason I switched to
Debian, was RedHat's broken GCC (2.96 I think), which I guess was just
included to pretend to be "cutting edge". Now, I recently installed a
RedHat 9, and with PlanetCCRMA on top, it is very nice, but running Debian
Sid does not feel less safe to me. And I would never run any mission-
critical servers with RedHat. Here Debian stable is the safest bet.
Anyway, I expect that I might switch to unstable, or at least testing, for
some of the workstations, when I feel that modifying stable becomes more work
and also more risky, than simply using unstable.
Maarten
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-07-23 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 17:33 Poll: Distro for audio and MIDI development Ismael Valladolid Torres
2003-07-23 22:28 ` Maarten De Boer [this message]
2003-08-04 11:11 ` Leandro Guimarães Faria Corsetti Dutra
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=Pine.LNX.4.44.0307232212360.29546-100000@iua-mail.upf.es \
--to=mdeboer@iua.upf.es \
--cc=alsa-devel@lists.sourceforge.net \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-audio-dev@music.columbia.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.