public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-announce@cygwin.com
Subject: Updated: _autorebase-001003-1
Date: Sun, 07 Feb 2016 10:05:00 -0000	[thread overview]
Message-ID: <87r3gorhnb.fsf@Rainer.invalid> (raw)


The _autorebase package has been updated with several improvements to
(hopefully) increase the robustness of the scripts and avoid some
spurious warning messages.


_autorebase
===========

This package provides scripts to keep the Cygwin system properly
rebased.  By default this happens incrementally, which means after
each run of setup.exe it is determined which packages have been newly
installed and only the dynamic objects provided by those packages are
rebased, taking the rebase map of the existing installation into
account.  The scripts are intended to be run by the system
administrator or from another account that has all the necessary
access rights.

Since over time the rebase map can fragment, it is possible to trigger
a full rebase.  In this case all packages on the system are treated as
newly installed and the existing rebase map is cleared before doing
the rebase.

Some programs allow the user to create or install dynamic objects
after installation.  Since these are not part of an installed package,
they wouldn't be rebased automatically, as their location isn't known.
Packages can make the potential locations of such dynamic objects
known by dropping a file (named after the package) in
/var/lib/rebase/dynpath.d/.  If any dynamic objects are installed by
users, these locations should be advertised in /var/lib/rebase/user.d/
(the file name should be identical to the user name if there are
multiple users on this system).  The format of these files is one
absolute path per line.  Those directory paths should not include
locations of packaged dynamic objects, as these are already picked up
from the installation.

The incremental rebase is controlled by the script /usr/bin/rebaselst.
Except for debugging purposes this script should not be run directly by
users, as (like any other attempt at rebasing) it doesn't work
correctly on a live Cygwin system.

To perform a full rebase, execute "rebase-trigger fullrebase".  Then
shut down Cygwin, including any services you have installed, and
simply run setup.exe.  The rebase will be performed even when the
installation did not get modified in any way.  Any subsequent runs of
setup.exe will again rebase in incremental mode.


-- 
              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

                 reply	other threads:[~2016-02-07 10:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87r3gorhnb.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-announce@cygwin.com \
    --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).