[hwloc-devel] Create success (hwloc r1.5a1r4454)

2012-04-25 Thread MPI Team
Creating nightly hwloc snapshot SVN tarball was a success. Snapshot: hwloc 1.5a1r4454 Start time: Wed Apr 25 21:01:01 EDT 2012 End time: Wed Apr 25 21:04:18 EDT 2012 Your friendly daemon, Cyrador

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Guy Streeter
On 04/25/2012 04:38 AM, Brice Goglin wrote: > Hello, > > We recently got some complains from redhat/centos users that wanted to install > hwloc on their cluster but couldn't because it brought so many X libraries > that they don't care about. > > Debian solves this by having two hwloc packages:

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Jeff Squyres
On Apr 25, 2012, at 11:18 AM, Samuel Thibault wrote: > But it still seems overkill to me to use approach 1 while approach 2 > just works. Yes, that conflicts with the original issue of the thread. > It happens that on Debian we can actually make hwloc and hwloc-nox > co-installable, by just

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Samuel Thibault
Jeff Squyres, le Wed 25 Apr 2012 17:11:28 +0200, a écrit : > Yes: the lstopo user gets whatever the sysadmin chose to install. > No: the system is not flexible for binary distributions > > Meaning: I see 2 ways to have binary packages that have X/cairo support and > don't have X/cairo support: >

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Jeff Squyres
On Apr 25, 2012, at 11:04 AM, Samuel Thibault wrote: >> Yes, understood, but my point here is that there could be multiple hwloc >> packages -- one that installs the core and some base set of lstopo plugins >> (probably not cairo and X). And then secondary packages install lstopo's >> cairo

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Samuel Thibault
Jeff Squyres, le Wed 25 Apr 2012 17:03:01 +0200, a écrit : > On Apr 25, 2012, at 10:58 AM, Samuel Thibault wrote: > > > It already adapts itself, here. The issue is that the user has to > > install an X version to get potential for X support. Which brings X. > > If you do this with plugins, and

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Jeff Squyres
On Apr 25, 2012, at 10:58 AM, Samuel Thibault wrote: > It already adapts itself, here. The issue is that the user has to > install an X version to get potential for X support. Which brings X. > If you do this with plugins, and you want automatic adaptation to > whether X is there, you'll have

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Samuel Thibault
Brice Goglin, le Wed 25 Apr 2012 16:58:16 +0200, a écrit : > On 25/04/2012 16:55, Jeff Squyres wrote: > >On Apr 25, 2012, at 10:48 AM, Samuel Thibault wrote: > > > >>>FWIW: Having lstopo plugins for output would obviate the need for having > >>>two executable names. > >>Well, it seems overkill to

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Samuel Thibault
Jeff Squyres, le Wed 25 Apr 2012 16:55:23 +0200, a écrit : > On Apr 25, 2012, at 10:48 AM, Samuel Thibault wrote: > > >> FWIW: Having lstopo plugins for output would obviate the need for having > >> two executable names. > > > > Well, it seems overkill to me. It makes sense to me to have both

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Brice Goglin
On 25/04/2012 16:55, Jeff Squyres wrote: On Apr 25, 2012, at 10:48 AM, Samuel Thibault wrote: FWIW: Having lstopo plugins for output would obviate the need for having two executable names. Well, it seems overkill to me. It makes sense to me to have both xlstopo and lstopo. Ick. FWIW, I

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Jeff Squyres
On Apr 25, 2012, at 10:48 AM, Samuel Thibault wrote: >> FWIW: Having lstopo plugins for output would obviate the need for having two >> executable names. > > Well, it seems overkill to me. It makes sense to me to have both > xlstopo and lstopo. Ick. FWIW, I dislike having two executables.

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Jeffrey Squyres
FWIW: Having lstopo plugins for output would obviate the need for having two executable names. On Apr 25, 2012, at 9:42 AM, Jiri Hladky wrote: > Hello, > > I would strongly vote to split the hwloc package to the core (ASCII only, > including ASCII only version of lstopo ) package and GUI

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Chris Samuel
On Wednesday 25 April 2012 19:38:00 Brice Goglin wrote: > How do people feel about this? It sounds like what you have is a conflict between the policies of Debian (and hence Ubuntu) and the expectations of RHEL/CentOS users. Debian Policy is fairly clear on this matter: # 11.8.1 Providing X

Re: [hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Ralph Castain
I don't have a strong opinion, but the historical "standard practice" for Linux/Unix has always been to default to cmd line, non-graphical interfaces. Graphical output was optional. Of course, that stemmed from the days before everyone had a graphical display, but it is still generally

[hwloc-devel] lstopo-nox strikes back

2012-04-25 Thread Brice Goglin
Hello, We recently got some complains from redhat/centos users that wanted to install hwloc on their cluster but couldn't because it brought so many X libraries that they don't care about. Debian solves this by having two hwloc packages: the main hwloc one, and hwloc-nox where cairo is