[repo.or.cz] unleashed-userland.git branch no-puname updated: v1.2-15-g6a83a6e0829e

lotheac lotheac at iki.fi
Thu Jan 3 20:27:10 UTC 2019


This is an automated email generated because a ref change occurred in the
git repository for project unleashed-userland.git.

The branch, no-puname has been updated
  discards  0e04061c6e75b0f9bd930631337f675ca87c62ee (commit)
  discards  ff985ebaf3c72eb14d48de604ca7089de04648fe (commit)
  discards  b4c4291ee740ff3f1122dfb5dac557c9ccb22982 (commit)
       via  6a83a6e0829eac6d7c2d488073c4502e81ebb9f3 (commit)
       via  1b8af4b6c3866fbfa10d53a65de1d8cc16ea93f1 (commit)
       via  efd7a7c4a7e1c6c34a85aa9a1f1a4ab5a8718c6f (commit)
       via  01e18d12dbfa385c6ea4c41e8feaad05e5d8ab3c (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (0e04061c6e75b0f9bd930631337f675ca87c62ee)
            \
             N -- N -- N (6a83a6e0829eac6d7c2d488073c4502e81ebb9f3)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 6a83a6e0829eac6d7c2d488073c4502e81ebb9f3
Author: Lauri Tirkkonen <lotheac at iki.fi>
Date:   Thu, 3 Jan 2019 19:56:55 +0200
URL:    <https://repo.or.cz/unleashed-userland.git/6a83a6e0829eac6d>

    libtool: don't attempt to regen configure
    
    libtoolize is a bad idea in libtool source; it just fails.

 components/developer/libtool/Makefile | 2 ++
 1 file changed, 2 insertions(+)

commit 1b8af4b6c3866fbfa10d53a65de1d8cc16ea93f1
Author: Lauri Tirkkonen <lotheac at iki.fi>
Date:   Thu, 3 Jan 2019 18:25:27 +0200
URL:    <https://repo.or.cz/unleashed-userland.git/1b8af4b6c3866fbf>

    configure.mk: if package uses libtool, regenerate ./configure
    
    libtool puts os-specific checks into ./configure, so we have to
    regenerate it. this might not work for every package; the "correct" way
    is to run the package's autogen.sh (if it has one) or some variation of
    autoreconf otherwise, but that approach sometimes runs into autotools
    version mismatches. so try to do the minimum work necessary.

 make-rules/configure.mk | 6 ++++++
 1 file changed, 6 insertions(+)

commit efd7a7c4a7e1c6c34a85aa9a1f1a4ab5a8718c6f
Author: Lauri Tirkkonen <lotheac at iki.fi>
Date:   Mon, 24 Dec 2018 21:46:03 +0200
URL:    <https://repo.or.cz/unleashed-userland.git/efd7a7c4a7e1c6c3>

    use gnu ld for everything
    

 make-rules/shared-macros.mk | 2 +-
 tools/Makefile              | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

commit 01e18d12dbfa385c6ea4c41e8feaad05e5d8ab3c
Author: Lauri Tirkkonen <lotheac at iki.fi>
Date:   Mon, 24 Dec 2018 21:18:17 +0200
URL:    <https://repo.or.cz/unleashed-userland.git/01e18d12dbfa385c>

    libtool: add unleashed support
    

 .../developer/libtool/patches/unleashed.patch | 68 +++++++++++++++++++
 1 file changed, 68 insertions(+)
 create mode 100644 components/developer/libtool/patches/unleashed.patch

-----------------------------------------------------------------------

Summary of changes:
 components/developer/libtool/Makefile         |  2 ++
 .../developer/libtool/patches/unleashed.patch | 25 +++++++++++++------
 make-rules/configure.mk                       |  8 +++++-
 3 files changed, 27 insertions(+), 8 deletions(-)


repo.or.cz automatic notification. Contact project admin jeffpc at josefsipek.net
if you want to unsubscribe, or site admin admin at repo.or.cz if you receive
no reply.
-- 
unleashed-userland.git ("Unleashed OS - userland")


More information about the Commits mailing list