Opened 18 years ago

Closed 11 years ago

#126 closed enhancement (wontfix)

LIBC: Provide binary runtime WPI archives

Reported by: dmik Owned by: bird
Priority: normal Milestone:
Component: libc Version:
Severity: normal Keywords: libc wpi
Cc:

Description

It will be handy to have an official binary distribution of the LIBC Runtime libraries as a WPI archive. This way, it will be possible to let WarpIn maintain package dependencies for applications using LIBC and thus simplify to resolve LIBC requirements for both application vendors packaging their products and end-users installing them.

Attachments (3)

warpin_scripts.zip (2.5 KB ) - added by dmik 18 years ago.
WarpIn scripts for LIBC
libc.wis (30.4 KB ) - added by dmik 18 years ago.
.wis script for kLIBC
wis-libc-0_6_2-csd2.zip (13.2 KB ) - added by dmik 17 years ago.
WPI scripts for kLIBC 0.6.2 CSD2

Download all attachments as: .zip

Change History (9)

by dmik, 18 years ago

Attachment: warpin_scripts.zip added

WarpIn scripts for LIBC

comment:1 by guest, 18 years ago

I've created installation scripts (see the attachment above).

I've also created the WPI and the EXE archive for the current LIBC runtime (0.6.1). They are currently in ftp://ftp.netlabs.org/incoming, but should later apparently move to ftp://ftp.netlabs.org/pub/gcc, where the ZIP archive lives.

comment:2 by dmik, 18 years ago

Releasing a new LIBC version is rather easy. All one have to do is to:

  1. Gather all libc*.dll and gcc*.dll files to a directory and specify this directory in the PACKAGE variable in the create_package.cmd script. Note that COPYING.LIB isn't necessary since it is contained in the WarpIn script and will be always displayed to the user during installation.
  1. Edit the <TITLE> tag and the PACKAGEID and TITLE attributes of the <PCK> tags in the libc.wis script, as well as the textual value of the <PCK> tag.

Note that the PACKAGEID value is the most important one. Its format is

<vendor>\<application>\<package>\<v_maj>\<v_min>\<v_rev>\<v_build>

<vendor> and <application> are unlikely to be changed. <package> needs to be changed with every next binary incompatible release. Not changing it will allow users to update the LIBC installation instead of installing a concurrent version separately, which is good for hot fix releases and such.

<v_maj>\<v_min>\<v_rev>\<v_build> is just a version number that fits the LIBC version just policy "out of the box" I think.

comment:3 by dmik, 18 years ago

Oops, there is no .wis script in the attached archive, strange. Ok, attaching it separately.

by dmik, 18 years ago

Attachment: libc.wis added

.wis script for kLIBC

comment:4 by dmik, 17 years ago

Uploaded WPI installers for kLIBC version 0.6.2 CSD2 to ftp://ftp.netlabs/incoming/gcc. To be moved to ftp://ftp.netlabs/pub/gcc later I guess.

by dmik, 17 years ago

Attachment: wis-libc-0_6_2-csd2.zip added

WPI scripts for kLIBC 0.6.2 CSD2

comment:5 by Yuri Dario, 17 years ago

I just uploaded new packages for 0.6.3 dlls to incoming/gcc-csd3/

Here are the command line commmands used to generate packages:

runwic libc-0_6_3-csd3.exe -s libc.wis -a 1 *.dll -U
runwic libc-0_6_3-csd3.wpi -s libc.wis -a 1 *.dll

runwic.cmd is included with warpin distribution.

comment:6 by dmik, 11 years ago

Resolution: wontfix
Status: newclosed

I don't think that this ticket is relevant any more. We dropped support for WPI in favor of RPM. Those who still want ZIP will get it from the LIBC distributor (i.e. Knut).

Note: See TracTickets for help on using tickets.