From: "Dr. Volker Zell" <dr.volker.zell@oracle.com>
To: Cygwin List <cygwin@cygwin.com>
Subject: cygport packaging question regading obsoleted packages
Date: Thu, 30 Aug 2012 20:38:00 -0000 [thread overview]
Message-ID: <7zligwqzxr.fsf@vzell-de.de.oracle.com> (raw)
Hi Yaakov
Is the following the "official" cygport method to create obsoleted packages ?
For example I want to obsolete from the nettle-2.4 package the runtime
parts by providing new empty tarballs so that users who will upgrade to
nettle-2.5 will get rid of unsued dll's related to nettle-2.4.
nettle-2.4-2.cygport
====================
CATEGORY="_obsolete"
SUMMARY="Removed package"
DESCRIPTION="Removed package"
HOMEPAGE="http://www.lysator.liu.se/~nisse/nettle/"
SRC_URI="http://www.lysator.liu.se/~nisse/archive/${P}.tar.gz
http://www.lysator.liu.se/~nisse/archive/${P}.tar.gz.sig"
abi=4_3
hogweed_abi=2_1
# Only the runtime packages should be obsoleted"
PKG_NAMES="lib${PN}${abi} libhogweed${hogweed_abi}"
libnettle4_3_CONTENTS= #empty
libhogweed2_1_CONTENTS= #empty
03:08 PM [507]> cygport nettle-2.4-2.cygport prep pkg
>>> Preparing nettle-2.4-2
*** Info: SOURCE 1 signature follows:
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Signature made Sat, Sep 03, 2011 3:04:13 PM CEST using DSA key ID A8F4C2FD
gpg: Can't check signature: public key not found
>>> Unpacking source nettle-2.4.tar.gz
>>> Preparing working source directory
*** Info: applying patch nettle-2.4-2.cygwin.patch:
patching file CYGWIN-PATCHES/README
*** Info: applying patch nettle-2.4-2.src.patch:
patching file Makefile.in
patching file configure.ac
patching file testsuite/Makefile.in
>>> Packaging nettle-2.4-2
>>> Creating binary package(s)
>>> libnettle4_3-2.4-2.tar.bz2
*** Info: Creating empty package
>>> libhogweed2_1-2.4-2.tar.bz2
*** Info: Creating empty package
*** Info: No debug files, skipping debuginfo subpackage
>>> Checking packages for missing or duplicate files
find: `*': No such file or directory
>>> Creating source patches
CYGWIN-PATCHES/README | 83 ++++++++++++++++++++++++++++++++++++++++++++++++++
Makefile.in | 16 +++------
configure.ac | 6 +--
testsuite/Makefile.in | 2 -
4 files changed, 92 insertions(+), 15 deletions(-)
>>> Creating source package
nettle-2.4-2.cygport
nettle-2.4-2.cygwin.patch
nettle-2.4-2.src.patch
nettle-2.4.tar.gz
nettle-2.4.tar.gz.sig
>>> libnettle4_3 requires:
>>> libhogweed2_1 requires:
This is what I get.
-rw-r--r--+ 1 vzell None 1085342 Aug 30 14:49 nettle-2.4-2-src.tar.bz2
-rw-r--r--+ 1 vzell None 14 Aug 30 14:49 libhogweed2_1-2.4-2.tar.bz2
-rw-r--r--+ 1 vzell None 14 Aug 30 14:49 libnettle4_3-2.4-2.tar.bz2
What about the "find: `*': No such file or directory" error ?
And should I put in the nettle-2.5-1.cygport an explicit
REQUIRES="libnettle4_3 libhogweed2_1"
so that these will be pulled in when somebody installs nettle-2.5 ?
(effectively it should delete the old dll's)
Thanks
Volker
--
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:[~2012-08-30 13:20 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=7zligwqzxr.fsf@vzell-de.de.oracle.com \
--to=dr.volker.zell@oracle.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).