This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: setup.exe and replacing of in-use files

Who is creating kde's setup.ini? Are they writing it by hand, or are they creating it from setup.hint files by using the 'upset' script?

If the former, then the human who wrote it is WRONG. the package name for the file 'kde-x-1.3.tar.bz2' is 'kde-x' -- so the @ line should be

@ kde-x


@ kde-x-1.3

If the latter, then the ONLY way 'upset' would generate an @ line of the form below, is if the human who wrote the setup.hint file put an @ line in THAT. (setup.hint doesn't need an @ line; remove it.)


Lapo Luchini wrote:

The package release field must be pure numeric. I.e. 2.2.2-1, not 2.2.2-b1.
If you want a beta tag on packages then try 2.2.2b-1. The package release
field provides no information about package status, just versioning. Use the
package version field to provide such information.


What about this one? It grows like [1.3-]*1.3 (i.e. 1.3, 1.3-1.3, 1.3-1.3-1.3...), is the release field also strictly necessary?

Directly from KDE's setup.ini:
@ kde-x-1.3
sdesc: "Patches for xfree 4.2.x (libXExt, libXft (qt3), Xwin)"
category: KDE-xfree
requires: cygwin XFree86-base
version: 1.3
install: kde-x-1.3.tar.bz2 1944453

I don't know yacc format enough to extract that information myself from iniparse.y.
But... steange inilex.l doesn't contain a token for "version:"... I guess I must study it a bit more.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]