xfs
[Top] [All Lists]

Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled?

To: xfs-oss <xfs@xxxxxxxxxxx>
Subject: Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled?
From: Linda Walsh <xfs@xxxxxxxxx>
Date: Tue, 02 Oct 2012 21:21:25 -0700
In-reply-to: <11246457.6091377.1349236739598.JavaMail.root@xxxxxxxxxx>
References: <11246457.6091377.1349236739598.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666


Nathan Scott wrote:
Mmm, wasn't trying to pass judgement there - I'm sure the OpenSuSE
package maintainer will take a patch to enable it in the spec file
there if its not in place.
----
Wouldn't bet on it...

I tried to get them to NOT issue a disabling patch for default parallelism
in upstream sort, and they said not unless I could prove it wouldn't cause a
a hang in their build process (when it was first implemented, their algorithm
had a few problems due to default buffer sizes on linux), but that was 2 years
ago and O.Suse still won't enable it - but you can specify that you want
parallel sort with every invocation -- which doesn't help for 3rd party progs
that just call sort (like updatedb) -- unless you modify them as well..

They also don't support build packages via source on a opensuse installation ---
as it has "superfluous" packages installed, and they don't want to test for
interactions anymore.

I felt even if they wanted a cleanroom for production -- they could still do
rpmbuilds with a a clean-distro devel install as a test step that things
worked together, but it seems like they are moving away from supporting direct
development or building of packages except via a special cleaned root.

Disappointing.

<Prev in Thread] Current Thread [Next in Thread>