bugPSPP - Bugs: bug #19069, Write more specific INSTALL file

 
 

bug #19069: Write more specific INSTALL file

Submitter:  Ben Pfaff <blp>
Submitted:  Fri 16 Feb 2007 07:28:30 PM UTC
   
 
Category:  Compilation/Portability Severity:  5 - Average
Status:  Fixed Assigned to:  None
Open/Closed:  Closed Release:  Before 0.6.0
Effort:  0.00
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 28 Jul 2007 02:42:48 AM UTC, comment #8: 


>...This is not true. I moved /usr/bin/pkg-config, and ran make
>distclean; ./configure and got: ...


You're right.  I think that this should be moved to the list of packages needed for GUI support.  Mind doing that?

>2. I'm not actually sure if it'll compile with gtk 2.6 anymore.
>There may be some 2.8 dependencies. Can anyone confirm that?


GTK+ 2.8.0 was released August 2005, so I think it'd be perfectly OK to just say that we need 2.8 even if we haven't actually checked if 2.6 works.

>3. I suggest the attached patch to README.


Looks good to me.  You can apply the same changes to the similar text in the Savannah description of PSPP.

Ben Pfaff <blp>
Group administrator
Sat 28 Jul 2007 02:30:49 AM UTC, comment #7: 

I'm reopening this, because I think there's more to do.


1. from INSTALL:
The following packages are optional.  They are useful primarily for
PSPP developers.

    * pkg-config (http://pkg-config.freedesktop.org/wiki/).  This is
      needed only to regenerate configure after modifying
      configure.ac.


This is not true. I moved /usr/bin/pkg-config, and ran make distclean; ./configure and got:


configure: error: The following required prerequisites are not installed.
You must install them before PSPP can be built:
        gtk+ 2.0 v2.6.0 or later (or use --without-gui)
        libglade 2.0 (or use --without-gui)


2.  I'm not actually sure if it'll compile with gtk 2.6  anymore.  There may be some 2.8 dependencies.  Can anyone confirm that?



3. I suggest the attached patch to README.

In particular, I'd like to expunge the sentance "[pspp] interprets commands in the SPSS language and produces ...", which  gives the impression that pspp is little more than a low level library or filter, without any user interface.  It may have been an accurate description at one time, but PSPP is much more than that now.


(file #13503)

John Darrington <jmd>
Group administrator
Fri 27 Jul 2007 09:38:14 PM UTC, comment #6: 

Thanks Jason.  I checked this in.

Ben Pfaff <blp>
Group administrator
Fri 27 Jul 2007 08:38:50 PM UTC, comment #5: 

Looks okay to me.

Jason H Stover <jstover>
Group Member
Fri 27 Jul 2007 07:14:23 PM UTC, comment #4: 

I've attached edits that IMO should be sufficient to close the bug:

  • Move prerequisites from README to INSTALL, to make INSTALL self-contained.


  • Make it clear at the top of INSTALL and in README that the instructions are PSPP-specific.  I for one tend to ignore INSTALL files because they're usually identical from package to package.   I don't want people to make that mistake with PSPP.


  • Be more verbose with prerequisites.  State what's optional and why you'd want to install it clearly.  Group prereqs by category.


  • Mention how to do private installs.


  • Mention how Cygwin and MinGW are known to work.


  • Move copyright info to end of INSTALL, to make it easier to read.


Comments?

(file #13498)

Ben Pfaff <blp>
Group administrator
Fri 13 Jul 2007 12:57:54 AM UTC, comment #3: 

I've committed this file then.  I'm leaving this bug open, to remind us to attend to the other things that Ben suggested.

John Darrington <jmd>
Group administrator
Thu 12 Jul 2007 04:46:47 AM UTC, comment #2: 

Thank you for working on this.  IMO your changes are OK to check in now.  We can always improve them later.

I think we should recommend mailing comment to bug-gnu-pspp instead of pspp-dev, so that users not subscribed don't have to jump through an extra hoop to help us out.

It might be nice to add a few words about how to do a private install, for users of a shared computer who do not have root, as is often the case on university Unix systems.  I have often done so by specifying --prefix=$HOME or --prefix=$HOME/inst to configure.  The former has the advantage that many systems automatically put $HOME/bin in $PATH if it exists; the latter clutters $HOME a little less.

It would be nice if someone (not necessarily you) would write up a few words about the various ways to compile PSPP under Windows.  John McCabe-Dansted seems to be knowledgable in this area, do you think he would be willing to help out?

Ben Pfaff <blp>
Group administrator
Thu 12 Jul 2007 04:23:40 AM UTC, comment #1: 

Here's a start of a more specific INSTALL file.  I haven't actually  talked about cross-compilation yet ...

(file #13293)

John Darrington <jmd>
Group administrator
Fri 16 Feb 2007 07:28:30 PM UTC, original submission:  

Currently we use a generic INSTALL file, but we should write something more specific to PSPP that in particular talks about cross-compiling.

(Reported by John Darrington as coment on bug #19003 originally, now filing as separate bug.)

Ben Pfaff <blp>
Group administrator

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #13503:  readme.patch added by jmd (3KiB - text/x-diff)
file #13498:  install-instructions.patch added by blp (11KiB - text/x-diff)
file #13293:  INSTALL added by jmd (6KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jstover (Posted a comment)
  • -email is unavailable- added by jmd (Updated the item)
  • -email is unavailable- added by blp (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 15 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-07-28 jmd StatusWorks For Me Fixed
        Open/ClosedOpen Closed
    2007-07-28 blp StatusIn Progress Works For Me
    2007-07-28 jmd Attached File- Added readme.patch, #13503
        Severity7 - Major 5 - Average
        StatusFixed In Progress
        Open/ClosedClosed Open
    2007-07-27 blp Open/ClosedOpen Closed
    2007-07-27 blp StatusReady for Test/Review Fixed
    2007-07-27 blp Attached File- Added install-instructions.patch, #13498
        StatusIn Progress Ready for Test/Review
    2007-07-25 blp ReleaseNone Before 0.6.0
    2007-07-13 jmd StatusWorks For Me In Progress
    2007-07-12 blp StatusNone Works For Me
    2007-07-12 jmd Attached File- Added INSTALL, #13293

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code