All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Davison <julian-xen_devel@tech.cbhs.school.nz>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [patch rfc 1/3] xen arch header rework.
Date: Wed, 18 Oct 2006 09:10:31 +1300	[thread overview]
Message-ID: <453538B7.7000508@tech.cbhs.school.nz> (raw)
In-Reply-To: <1161091719.4263.58.camel@localhost.localdomain>

Jacob Gorm Hansen wrote:
> On Mon, 2006-10-16 at 10:56 -0400, Steven Rostedt wrote:
> 
>>> The following packages will be REMOVED:
>>>   alien build-essential debhelper defoma dpkg-dev ethereal fontconfig
>>>   intltool-debian libcompress-zlib-perl libfontconfig1 libft-perl
>>>   libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libmail-sendmail-perl
>>>   libpango1.0-0 libpango1.0-common libxft2 ntp ntp-server ntp-simple
>>>   perl perl-doc perl-modules po-debconf rpm ttf-bitstream-vera xterm
>>> 0 upgraded, 0 newly installed, 28 to remove and 0 not upgraded.
>>> Need to get 0B of archives.
>>> After unpacking 59.8MB disk space will be freed.
>>> Do you want to continue? [Y/n] n
>>> Abort.
> 
> I guess I just cannot fathom the infinite wisdom that leads to a widget
> toolkit or a truetype font requiring a script language interpreter to
> run. This example describes perfectly why Linux will never be a serious
> threat to any of the real desktop platforms out there, most of the
> application code is so tangled up in external dependencies that
> packaging up software stand-alone is practially impossible, version
> conflicts (two applications requiring different version of say, perl)
> are inevitable, and performance just plain sucks, because developers
> prefer comfortable (perl, python) to fast and predictable (C, C++). Oh
> well.

I'm with Steven in that we're getting well off topic here,
but I'm not in any way convinced this is unique to Linux.
Nor am I certain that's an accurate evaluation of those
languages :)
But this isn't the place.

> Xen already requires python, so using python instead of perl in the
> build script does not further bloat the requirements list.

I think ultimately this is what it comes down to.
The more consistent the code/utility base the better
it is for maintainers and builders.

-- 
Julian Davison
Note: 1) This may have come from an address @cbhs.school.nz
          but isn't necessarily the (or even an) official view
          of Christchurch Boys' High School
       2) While replying to this address may get into my mailbox
          it will almost certainly be filtered into a mailing list
          folder. To actually reach actual me, strip off the bit
          after the '-' in the name.

  reply	other threads:[~2006-10-17 20:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05  9:05 [patch rfc 0/3] xen arch header patches kraxel
2006-10-05  9:05 ` [patch rfc 1/3] xen arch header rework kraxel
2006-10-05 12:27   ` Jan Beulich
2006-10-05 13:08     ` Gerd Hoffmann
2006-10-11  9:16     ` Gerd Hoffmann
2006-10-11  9:44       ` Keir Fraser
2006-10-11 10:40         ` Jacob Gorm Hansen
2006-10-11 10:50           ` Keir Fraser
2006-10-11 11:54             ` Gerd Hoffmann
2006-10-11 13:47               ` Jacob Gorm Hansen
2006-10-11 14:49                 ` Gerd Hoffmann
2006-10-11 20:38               ` Julian Davison
2006-10-14  1:30                 ` Steven Rostedt
2006-10-15 20:21                   ` Julian Davison
2006-10-16 14:56                     ` Steven Rostedt
2006-10-17 13:28                       ` Jacob Gorm Hansen
2006-10-17 20:10                         ` Julian Davison [this message]
2006-10-11 11:39         ` Gerd Hoffmann
2006-10-11 11:43           ` Keir Fraser
2006-10-11 12:21             ` SPAM: " Gerd Hoffmann
2006-10-11 12:04         ` John Levon
2006-10-05  9:05 ` [patch rfc 2/3] xen arch header rework, fixups kraxel
2006-10-05  9:05 ` [patch rfc 3/3] xen arch header rework, check utility kraxel

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=453538B7.7000508@tech.cbhs.school.nz \
    --to=julian-xen_devel@tech.cbhs.school.nz \
    --cc=xen-devel@lists.xensource.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 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.