Opened 2 years ago

Closed 13 months ago

#352 closed task (implemented)

Remove license text from WIS (and call from pck 1)

Reported by: Lewis Rosenthal Owned by: Gregg Young
Priority: minor Milestone: 1.4.1
Component: Packaging Version: 1.4.0
Keywords: Cc:

Description

The main WIS is way too large. These licenses should not be entered explicitly in here, and instead, should just be called from the source pack, i.e.:

<README FORMAT=PLAIN EXTRACTFROMPCK="1">LICENSE.CDDL</README>

Attachments (2)

lucide.wis (50.4 KB) - added by Lewis Rosenthal 17 months ago.
Uncommittted WIS used for 1.4.0 manual repack
lucide_de.wis (965 bytes) - added by Lewis Rosenthal 17 months ago.
German 1.4.0 WIS, typical of other language packs

Download all attachments as: .zip

Change History (8)

comment:1 Changed 17 months ago by Lewis Rosenthal

The problem I see with this approach, however, is that WarpIN will ignore everything after the first set of README tags on a given page. We have two licenses to display, namely, CDDL and LGPL. In order to accommodate these, we'll need to insert a second license page (or third, as the opening text is also part of the current README tag, in HTML).

Changed 17 months ago by Lewis Rosenthal

Attachment: lucide.wis added

Uncommittted WIS used for 1.4.0 manual repack

Changed 17 months ago by Lewis Rosenthal

Attachment: lucide_de.wis added

German 1.4.0 WIS, typical of other language packs

comment:2 Changed 17 months ago by Gregg Young

Owner: changed from Lewis Rosenthal to Gregg Young
Status: newassigned

comment:3 Changed 17 months ago by Gregg Young

Lewis can you please post the cmd you used for building the 1.4.0 wpi? Thanks

comment:4 Changed 17 months ago by Gregg Young

Why was the NSL REXX removed and why is there a separate wis for the NSLs? I assume you want all the readme/license pages to open a file instead of being inline. We have a ticket requesting additional associations. I don't think we should do associations for the image files since there are other (better) tools for them in common use (PMView). Can we add an association without making it the default?

It appears that if someone says they don't want Lucide associated with pdfs that it deletes the ini keys. This isn't what we want is it? That would disassociate everything from pdfs and remove the filters and types or am I missing something.

comment:5 Changed 17 months ago by Gregg Young

I have started merging the wis.tpl with the 1.40 wis. Need to do the following;

1. Add files: 
Lucide_en.hlp 
GMB plugin help (still need this from Lewis)
lugbm.cfg

2. Add env
GBM name
for selecting the languages we don't have wis translations for;

3. Replace or remove code that removes ini association keys. 

4. Put .lng and readme files in correct language package (not all in package 1)

comment:6 Changed 13 months ago by Gregg Young

Resolution: implemented
Status: assignedclosed
Note: See TracTickets for help on using tickets.