RE: Incorrect version in packages names
The naming was probably inherited from linux, where it is possible to have both kde (1) and kde (2) and kde (3) all installed on the same machine. Therefore, each needs different basename. Yes, this is it. If the kde-cygwin folks want to maintain that package-name distinction, then they should just use kdelibs_2 instead of kdelibs-2 as their basename. Then upset and setup will be happy -- and end users will be able to install both kdelibs_2 and kdelibs_3. Thanks for this hint. Ralf
RE: Incorrect version in packages names
The naming was probably inherited from linux, where it is possible to have both kde (1) and kde (2) and kde (3) all installed on the same machine. Therefore, each needs different basename. If the kde-cygwin folks want to maintain that package-name distinction, then they should just use kdelibs_2 instead of kdelibs-2 as their basename. Then upset and setup will be happy -- and end users will be able to install both kdelibs_2 and kdelibs_3. What about kde-x. Must it be named kde_x ? Ralf
RE: Incorrect version in packages names
What about kde-x. Must it be named kde_x ? Couln't those fixes be included in the base xfree package? Having a package that overwrites a file from another package gives problems if you deinstall the latter: you lose the file from the first... Unfortunally for some reasons no, because 1. this patches relates to cygipc based shm support, which isn't a cygwin packages and should not be used in a cygwin package (the xfree packages). There were some threads relating to this topic in the past on cygwin/cygwin apps. At the time the shm support will be a stable part of the cygwin dll, xfree could be recompiled with shm support. 2. some patches are currently not part of the official xfree release yet (for example xft patches and ice delay patch, see release notes below) Release 1.3 libXft: - added qt3 symbols to Xftlib libICE: - removed 5 seconds delay in libICE if file attributes don't match Release 1.2 - renamed package to kde-x Xwin.exe: - added MIT-SHM extension Ralf
Re: Incorrect version in packages names
Ralf Habacker wrote: The naming was probably inherited from linux, where it is possible to have both kde (1) and kde (2) and kde (3) all installed on the same machine. Therefore, each needs different basename. If the kde-cygwin folks want to maintain that package-name distinction, then they should just use kdelibs_2 instead of kdelibs-2 as their basename. Then upset and setup will be happy -- and end users will be able to install both kdelibs_2 and kdelibs_3. What about kde-x. Must it be named kde_x ? No, kde-x is fine. The problem is, the parser can't tell if the grouping after a '-' is part of the package name or package version, when the grouping begins with a numeral. kde-2 -- confusinng kde-x -- not confusing --Chuck
Re: Incorrect version in packages names
- Original Message - From: Christopher Faylor [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 08, 2002 4:16 PM and in setup.ini : @ kdelibs-2 Get rid of this. I suspect that it is confusing setup.exe. It should certainly do the right thing without it. Doh!. Good catch Chris. Yes, foo-bar is allowable as a package name, foo-2 is not. I'll see what I can do for a future setup.exe release to address this, but don't expect anything soon. It'll require altering the installed.db database format, which results in a non-backwards compatible local environment. Rob
Re: Incorrect version in packages names
- Original Message - From: Christopher Faylor [EMAIL PROTECTED] To: [EMAIL PROTECTED] upset would probably do the right thing with the above but I really don't see any reason to use it, regardless. I don't see any reason why a user would need to know that these are kdelibs-2 when it is pretty obvious from the version number. One possibility is if the version number reflects the ABI, not the software release. This is actually quite likely with libtool packages. Anyway, it's low priority however one approaches it. Rob
Re: Incorrect version in packages names
Christopher Faylor wrote: upset would probably do the right thing with the above but I really don't see any reason to use it, regardless. I don't see any reason why a user would need to know that these are kdelibs-2 when it is pretty obvious from the version number. The naming was probably inherited from linux, where it is possible to have both kde (1) and kde (2) and kde (3) all installed on the same machine. Therefore, each needs different basename. If the kde-cygwin folks want to maintain that package-name distinction, then they should just use kdelibs_2 instead of kdelibs-2 as their basename. Then upset and setup will be happy -- and end users will be able to install both kdelibs_2 and kdelibs_3. --Chuck
Re: Incorrect version in packages names
and in setup.ini : kdelibs-2 Get rid of this. I suspect that it is confusing setup.exe. Found in /etc/setup/installed.db : kde-x-1.2 kde-x-1.2-1.2-1.2-1.2-1.2-1.2-1.2-1.2-1.2.tar.bz2 0 kde-x-1.3 kde-x-1.3-1.3-1.3-1.3-1.3-1.3-1.3-1.3-1.3.tar.bz2 0 kdebase-2 kdebase-2-2-2-2-2-2-2-2-2.2.2-b1.tar.bz2 0 kdelibs-2 kdelibs-2-2-2-2-2-2-2-2-2.2.2-b1.tar.bz2 0 ___ Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
