This is the mail archive of the cygwin-patches@cygwin.com 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: setup.exe remove scripts [Was: Re: experimental texmf packages]


"Robert Collins" <robert.collins@itdomain.com.au> writes:

> Right, this is now in CVS> Sorry about the muckup.

Ok, thanks, it's there.

How should errors in postinstall scripts be handled?  It is tempting
to replace

    postinstall.cc:
    find (cygpath ("/etc/postinstall", 0), run_script_in_etc_postinstall);

with something vaguely like

   for (size_t n = 1; n <= db.packages.number (); n++)
     if (try_run_script ("/etc/postinstall/", name))
       warning ("postinstall of %s failed"
                "please examine or rerun /etc/postinstall/%s.sh manually",
                name, name));

But, afaik, there's no need for a package's postinstall script to be
called '<pkg->name>.sh'?  Should/can we enforce something like this?

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org


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