From: Linda Walsh <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled?
Date: Tue, 02 Oct 2012 21:21:25 -0700 [thread overview]
Message-ID: <506BBD45.90308@tlinx.org> (raw)
In-Reply-To: <11246457.6091377.1349236739598.JavaMail.root@redhat.com>
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.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-03 4:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 16:44 Why xfs_<utils> not 'readline' w/line-edit & history enabled? Linda Walsh
2012-10-02 18:41 ` Kinzel, David
2012-10-02 20:17 ` Dave Chinner
2012-10-02 21:29 ` Linda Walsh
2012-10-03 2:06 ` Eric Sandeen
2012-10-03 2:16 ` Nathan Scott
2012-10-03 3:51 ` Linda Walsh
2012-10-03 3:58 ` Nathan Scott
2012-10-03 4:21 ` Linda Walsh [this message]
2012-10-04 12:12 ` David Disseldorp
2012-10-02 21:30 ` Linda Walsh
2012-10-02 21:34 ` Linda Walsh
2012-10-02 21:52 ` Dave Chinner
2012-10-02 22:52 ` Why xfs_<utils> not 'readline' w/line-edit & history enabled? (+attachment) Linda Walsh
2012-10-02 23:14 ` Dave Chinner
2012-10-02 23:34 ` Linda Walsh
2012-10-02 23:50 ` Dave Chinner
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=506BBD45.90308@tlinx.org \
--to=xfs@tlinx.org \
--cc=xfs@oss.sgi.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.