Re: Package categorization inconsistencies

2014-01-24 Thread Corinna Vinschen
On Jan 21 19:03, Warren Young wrote:
 While doing my how big is a full Cygwin installation research[*],
 I came across some inconsistencies in package categorization:
 
 
 perl_debuginfo: Not in the Debug category.  It is also the only
 package named *_debuginfo instead of *-debuginfo
 
 cdrkit-doc, fftw33-doc, flac-docs, gsl-doc, gtk-doc,
 ImageMagick-doc, libcaca-doc, libcloog-isl-doc, libdatrie-doc,
 libgmp-doc, libgstreamer1.0-doc, libisl-doc, liblapack-doc,
 libmpc-doc, libmpfr-doc, libpoco-doc, libsigc2.0-doc, libthai-doc,
 libunistring-doc, libxcb-doc, libxml2-doc, libxslt-doc, libxslt2-doc,
 llvm-doc, octave-doc, postgresql-doc, ppl-doc, qt4-doc, ruby-doc,
 texlive-collection-*-doc, tiff-doc: Not in Doc category

I just checked the Fedora packages, and it turns out that they have the
same inconsistencies.  Sometimes the docs are part of the base package,
sometimes they are in the same group as their base package, sometimes
they are in the Documentation group, sometimes in
Applications/Publishing.  Sometimes the package is called -doc,
sometimes -docs.

Nothing to worry about I guess.

Corinna

 glproto, presentproto, xextproto, xproto: In Devel category, but not
 X11 category, yet they are part of X11.  And, vice versa: the other
 *proto packages that are in X11 probably should be in Devel, too.

That might in fact be helpful.


Corinna

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


pgp2trezH9nyh.pgp
Description: PGP signature


Re: setup wants to install new packages

2014-01-24 Thread Corinna Vinschen
On Jan 23 19:49, Andrew Schulman wrote:
 I reported this problem a few months ago.  Now I have a screenshot to
 show it:  http://postimg.org/image/e5uzokbn9/
 
 My last setup run was about a week ago.  I just started
 setup-x86_64.exe, and OOTB it wants to install 9 new packages.  I didn't
 select them, and they're not required - setup just selected them for me.
 Does anyone know why?

If you'd seen the setup code, you wouldn't ask that ;)

 Anyone else ever see this?

Not me.

 BTW this is a transient problem:  when I exit setup and restart, the new
 packages aren't selected again.

Weird.  I guess, somebody having this problem would have to debug
this.  /nudge


Corinna

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


pgpcURdGtVT1h.pgp
Description: PGP signature


Re: [ITA] Git et al

2014-01-24 Thread Eric Blake
On 01/15/2014 04:06 AM, Adam Dinwoodie wrote:
 On 13 January 2014 23:58, Adam Dinwoodie wrote:
 On 13 January 2014 21:32, Eric Blake wrote:
 That said, while I don't have as much time for cygwin packaging, I
 still DO plan on using git on cygwin, so I at least want to make sure
 my use cases still work when upgrading to the build you just provided
 before we actually upload it.

 It may still be a few days before I can test that your new packaging
 works for me (I'd welcome a review from anyone else as well), but the
 overall idea of adopting the package from me seems reasonable.

 There's already a known, fairly major problem with my build, reported by
 Steven Penny[0].  I'm hoping to get a fix to that out tomorrow evening.

 [0]: http://cygwin.com/ml/cygwin/2014-01/msg00086.html
 
 There's a new build available at http://tastycake.net/~adam/cygwin/
 which resolves that issue.  If you want to give it a try and let me know
 how you get on, I'd be exceedingly grateful.

I've now had a chance to test this, and at least my use cases worked.  I
can't say I used ALL of git functionality, but what I did use shows that
your build is good.  Let's go ahead and pass the maintainer baton.

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature


Re: Package categorization inconsistencies

2014-01-24 Thread Warren Young

On 1/24/2014 02:32, Corinna Vinschen wrote:

Nothing to worry about I guess.


I posted mainly for the maintainers, who may want to change their 
setup.hint files before their next upload.