Re: 64 bit: "noarch" packages and going beta

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Apr 10 23:28, Yaakov (Cygwin/X) wrote:
> On 2013-04-10 08:16, Corinna Vinschen wrote:
> >- Does anybody know of a simple way to find out which packages in the 32
> >   bit distro are actually "noarch' packages?  The reason I'm asking is
> >   that I'm looking for a simple way to fill up the 64 bit distro with
> >   all the packages which don't come with binaries, but consist entirely
> >   of scripts and docs.
> 
> This should get us started:
> 
> for p in $(find release/ -name '*[0-9].tar.bz2');
> do
>   if [ $(wc -c $p | cut -d' ' -f1) -gt 46 ] \
>      && [ -f ${p%\.tar\.bz2}-src.tar.bz2 ] \
>      && [ $(find ${p%/*} -name setup.hint | wc -l) -eq 1 ];
>   then
>     tar tf $p|grep -Eq '\.(exe|dll|so|a|cmxs|oct|dbg)' || echo ${p%/*};
>   fi;
> done

Thanks!

> However, I still think that separate i686/x86_64/noarch trees is the
> way to go, otherwise those using both Cygwins will end up needlessly
> downloading the same package twice, which doesn't happen on multilib
> Linux distributions (even when there are two copies on the server).

We could just symlink the directories of noarch packages into the 64 bit
release.  This would be a clear marker that the package doesn't contain
binaries.

Other than that, I'm still leaning towards an extra noarch directory,
too.  It looks like the much cleaner approach.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat