bugPSPP - Bugs: bug #48829, show all include postgresql...


bug #48829: show all include postgresql availability

Submitted by:  Harry Thijssen <unknown_one>
Submitted on:  Fri Aug 19 16:54:38 2016  
Category: Compilation/PortabilitySeverity: 1 - Wishlist
Status: NoneAssigned to: None
Open/Closed: OpenRelease: None
Effort: 0.00

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

Please log in, so followups can be emailed to you.


(Jump to the original submission Jump to the original submission)

Thu Aug 25 05:19:22 2016, comment #7:

I agree that a command line option such as --config would be more in line with the Gnu way of doing things. On the other hand spss, which we claim to emulate, apparently puts this information under SHOW ALL.

There is no reason why we couldn't do both.

John Darrington <jmd>
Project Administrator
Mon Aug 22 17:10:26 2016, comment #6:

I think it is usefull for bug hunting. If a user has a problem and can generate as much info as possible as easy as possible and send it.

If I see how this is handled in SPSS I guess show all is the most likely place.

Harry Thijssen <unknown_one>
Mon Aug 22 15:43:58 2016, comment #5:

> It's true that some of the implementation detail would be exposed. Is that necessarily bad? My concern is doing it in a way which would continue to be maintainable.

I guess it wouldn't hurt anything, although a lot of users probably wouldn't understand what it meant.

Is this more useful as a runtime command or as something to show in, say, --version output? What's the proposed use case for the information, in other words?

Ben Pfaff <blp>
Project Administrator
Mon Aug 22 04:53:30 2016, comment #4:

We already have a message like Ben suggests. However what Harry wants (I think) is a summary of optional features enabled (or not) when the software was built.

It's true that some of the implementation detail would be exposed. Is that necessarily bad? My concern is doing it in a way which would continue to be maintainable.

John Darrington <jmd>
Project Administrator
Mon Aug 22 01:18:02 2016, comment #3:

The COMPILE-OPTIONS that you suggest exposes a lot of implementation detail, I think.

It's not too hard to add a line like: "PostgreSQL is (not) supported," I guess.

Ben Pfaff <blp>
Project Administrator
Sun Aug 21 09:15:34 2016, comment #2:

I think grouping the output could be usefull. For example phpinfo gives nices and usefull info I think. Also in spss the current show info does some grouping of the info.

I would prefer a table with the compile time options.

Harry Thijssen <unknown_one>
Sat Aug 20 19:21:33 2016, comment #1:

I'm thinking about how this could best be done.
I'm a bit worried about a possible proliferation of entries in SHOW ALL.
How would it be if we had a single entry containing a concatenated string of all compile time options?

For example



John Darrington <jmd>
Project Administrator
Fri Aug 19 16:54:38 2016, original submission:

is it possible to include a message in show all if pspp was compiled with postgresql support?

Harry Thijssen <unknown_one>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by blp (Posted a comment)
  • -unavailable- added by jmd (Posted a comment)
  • -unavailable- added by unknown_one (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon Aug 22 04:53:30 2016jmdSeverity5 - Average=>1 - Wishlist

    Back to the top

    Powered by Savane 3.1-cleanup1