patchPSPP - Patches: patch #6262, How to not install developers...

 
 

You are not allowed to post comments on this tracker with your current authentification level.

patch #6262: How to not install developers guide by default?

Submitted by:  Ben Pfaff <blp>
Submitted on:  Fri 09 Nov 2007 06:13:58 AM UTC  
 
Category: NoneItem Group: None
Status: In ProgressAssigned to: None
Open/Closed: Open

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

Sun 11 Nov 2007 07:20:29 AM UTC, comment #6:

noinst_TEXINFOS is what I would have tried. I don't have any other suggestions.

John Darrington <jmd>
Project Administrator
Sun 11 Nov 2007 05:52:00 AM UTC, comment #5:

>I think it's a good idea to put such information into CVS, and
>perhaps into the released tarball, even if it's not complete.


Thanks. For now, I've checked this in.

>I think that developer information, whether complete or not,
>shouldn't get installed by default. It should have a seperate
>install target, eg: make install-dev-info


I don't know a way to do that with Automake. It could be approximated by using noinst_TEXINFOS, but noinst_TEXINFOS doesn't work in Automake 1.10 (or presumably earlier versions). I've reported this bug to bug-automake just now.

I can think of a couple of other ways to do this, but none of them really make me happy. Do you have a suggestion?

Ben Pfaff <blp>
Project Administrator
Sun 11 Nov 2007 02:35:59 AM UTC, comment #4:

Ben wrote:

> Do you like the idea of making this part of the release, even if it is not significantly expanded?


I think it's a good idea to put such information into CVS, and perhaps into the released tarball, even if it's not complete. However I think that developer information, whether complete or not, shouldn't get installed by default. It should have a seperate install target, eg: make install-dev-info

John Darrington <jmd>
Project Administrator
Sat 10 Nov 2007 06:08:01 AM UTC, comment #3:

>1. In the dvi version, the references to the user manual sections
>don't seem to get resolved properly.


I hadn't even tried formatting it as DVI or PDF. Thanks, I fixed this and some other damage besides (e.g. the title pages looked bad).

>2. It might be a good idea to put the developer manual sections in
>a seperate directory.


OK, good idea. I moved most of the files in the developer manual to doc/dev. I left pspp-dev.texi in doc, because this allows links between the two manuals to function before the manuals are installed (otherwise, Info readers only look in the same directory).

Here's an updated patch. Any further comments? Do you like the idea of making this part of the release, even if it is not significantly expanded?

>3. There seems to be some damage here:


Those are fragments of writing that I didn't finish. Removed.

(file #14353)

Ben Pfaff <blp>
Project Administrator
Fri 09 Nov 2007 11:22:11 PM UTC, comment #2:

1. In the dvi version, the references to the user manual sections don't seem to get resolved properly.

2. It might be a good idea to put the developer manual sections in a seperate directory.

3. There seems to be some damage here:

@node Cases
@section Cases

A

The set of variables is ordered

John Darrington <jmd>
Project Administrator
Fri 09 Nov 2007 06:16:41 AM UTC, comment #1:

Oops--replace with slightly better version.

(file #14345)

Ben Pfaff <blp>
Project Administrator
Fri 09 Nov 2007 06:13:58 AM UTC, original submission:

Here is the start of a developer's guide for PSPP. I have been sitting on it for months, hoping that I would find time to finish it up. But it's become apparent that that is not going to happen before the release of 0.6.0. So I'd like to check in what's here.

The manual includes a significant amount of advice and rationale. If you disagree with it, please say so.

The change set also includes a number of cleanups that I discovered should be done while I was writing the manual. Please, say so if you do not like any of these.

Ben Pfaff <blp>
Project Administrator

 

Attached Files
file #14353:  developers-guide-start-3.patch added by blp (321kB - text/x-diff)
file #14345:  developers-guide-start-2.patch added by blp (217kB - text/x-diff)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by jmd (Posted a comment)
  • -unavailable- added by blp (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):

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sun 11 Nov 2007 05:52:00 AM UTCblpStatusReady For Test/Review=>In Progress
      SummaryStart of developer\'s manual; cleanups=>How to not install developers guide by default?
    Sat 10 Nov 2007 06:08:01 AM UTCblpAttached File-=>Added developers-guide-start-3.patch, #14353
    Fri 09 Nov 2007 06:16:41 AM UTCblpAttached File-=>Added developers-guide-start-2.patch, #14345
    Fri 09 Nov 2007 06:15:54 AM UTCblpAttached File#14344=>Removed
    Fri 09 Nov 2007 06:13:58 AM UTCblpAttached File-=>Added developers-guide-start-2.patch, #14344

    Back to the top


    Powered by Savane 3.1-cleanup