public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128]
Date: Thu, 30 May 2013 00:43:00 -0000	[thread overview]
Message-ID: <51A6948B.3000807@users.sourceforge.net> (raw)
In-Reply-To: <51A684AA.2060904@cwilson.fastmail.fm>

Sorry for missing this before.

On 2013-05-29 17:43, Charles Wilson wrote:
> Known issue, waiting for cygport fix.  cygutils relies on cygport
> auto-generating the postinstall scripts which invoke those tools.
> Cygport does this because the install package contains the following two
> files:
>
> /usr/share/applications/cygstart.desktop
> /usr/share/mime/packages/cygutils.xml
>
> ...and it generates the postinstall script unconditionally (e.g. I can't
> turn it off) and the generated postinstall scripts themselves call the
> tools unconditionally.  Cygport also automatically adds the packages
> which contain those tools to the requires: field of the setup.hint,
> so...under normal circumstances, everything should be fine.

Right, because packages providing those kind of files usually need those 
commands to be run in order for them to take effect; see below.

> However, at user request I've manually removed the requires: line,
> because the addition of these two files to the cygutils package
> shouldn't have the effect of pulling *PERL* into the Base category. I
> assumed we'd live with the semi-brokenness for a few days, until...

Perl?  I thought it was Python, due to a false positive in the 
dependency detection with glib2.0, which I fixed on sourceware.

But now that you mention it, is cygutils *supposed* to be in Base?  It 
is marked category: Utils, but seems to be pulled into Base only because 
of cygwin-doc (which *is* in Base, oddly enough; shouldn't it just be 
Doc?) listing it as a dependency.

> ...I'm waiting for Yaakov to say whether this should be "fixed" in
> cygport [1], or if I should override all the auto-generation stuff by
> manually creating an explicit postinstall script (with suitable tool
> existence checks) and setup.hint.

The "problem" here is that cygutils is not primarily a desktop-oriented 
package.  Most packages providing XDG menu and mime entries *are*, so 
these dependencies not only mandatory, but quite modest by those 
standards.  I added these files because it allows better integration 
between desktop file managers 
(Nautilus/Caja/Thunar/PCManFM/Dolphin/etc.) and Windows, e.g. making it 
easy to launch an EXE/MSI installer from one's Downloads folder. 
However, most people use cygutils outside of the desktop, so 
particularly if its pulled into Base, these deps would be more than the 
bare-minimal system.

If cygutils should be in Base, the "solution" is probably one of the 
following:

* provide these files (and postinstall scripts) in a 'cygutils-x11' 
subpackage;

* OR move them to another package (not sure which yet) which will 
already be installed in desktop scenarios, and adding cygutils as a 
dependency thereto.

For now, should we go with the first option?


Yaakov


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-05-29 23:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 16:04 cygutils Postinstall Script Errors With Exit Code 128 Reini Urban
2013-05-29 19:50 ` Paul.Nickerson
2013-05-29 23:51 ` Attn: Yaakov [Was: Re: cygutils Postinstall Script Errors With Exit Code 128] Charles Wilson
2013-05-30  0:43   ` Yaakov (Cygwin/X) [this message]
2013-05-30 10:27     ` Corinna Vinschen
2013-05-30 21:26       ` Charles Wilson
2013-05-31  8:51         ` Corinna Vinschen
2013-06-05 16:47           ` Yaakov (Cygwin/X)
2013-06-06 15:17             ` Charles Wilson
2013-05-30 20:50     ` Charles Wilson
2014-07-16  1:54 ` cygutils Postinstall Script Errors With Exit Code 128 dylanhay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51A6948B.3000807@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).