This is the mail archive of the cygwin-apps 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: Release directories (was Re: [PATCH] setup: port to 64-bit, part 1)


On 3/14/2013 3:01 AM, Yaakov (Cygwin/X) wrote:
On Wed, 13 Mar 2013 12:51:18 +0100, Corinna Vinschen wrote:
If Yaakov applied the changes necessary to get the 64 bit setup running
for a start, would it be possible to let upset create a setup64.ini file
for the current cygwin/64bit/release test area?

Before we do that, I think we need to consider a bit of reorganization. As in any binary distribution, there are many "noarch" packages which could be used for both i686 and x86_64. Providing two identical copies is just a waste of storage and bandwidth for sourceware, mirrors, and users.

Instead, I think it would make sense to make three sibling trees, one
for i686 (the current release/ directory), one for x86_64, and one for
noarch packages.  Then, there would be two scans by upset: setup.ini
from i686 and noarch, and setup64.ini from x86_64 and noarch.

Thoughts?


Yaakov



in that case we need to assure same package name.


Just noted:

64 bit
$ tar -tf readline-6.2-1.tar.bz2 |grep dll
usr/bin/cyghistory7.dll
usr/bin/cygreadline7.dll

32 bit
$ cygcheck -f /usr/bin/cygreadline7.dll
libreadline7-6.1.2-3


and it is not the only one


Marco


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