public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] Updated: cygport-0.10.10-1
Date: Mon, 02 Apr 2012 03:56:00 -0000	[thread overview]
Message-ID: <announce.4F7922A9.1090207@users.sourceforge.net> (raw)

I have just released cygport-0.10.10 for the Cygwin distribution and the
Fedora Cygwin repository.  New features in this release:

* Documentation is nearly complete.  Please let me know (via the list) 
if there is anything else which should be documented, or anything which 
should be fixed or added to the existing documentation.

* Only shared libtool libraries are built by default.  If you absolutely 
need static libraries (and if you're not absolutely sure why, you 
don't), add --disable-static to cygconf or CYGCONF_ARGS.

* .tar.lrz tarballs are now supported (requires lrzip).

* The "download" command only downloads source files/patches which are 
not already present.  If you need to replace these files with newly 
downloaded copies, use the "downloadall" command.

Changes in this release (21):
       mirrors: use new KDE mirror redirector
       xorg: add SRC_URI and GIT_URI for drivers
       unpack: add support for .tar.lrz
       autotools: disable static libtool libraries by default
       Add convenience function for static-only embedded targets
       Add another convenience function for static-only embedded hosts
       claws-mail: set KEEP_LA_FILES to none
       spec: do not rely on redhat-rpm-config behaviour
       dodoc: install directories recursively
       Differentiate between downloading all sources or only missing ones
       doc: fix S documentation
       doc: document packaging variables
       doc: add introduction
       doc: add to usage, format, and packaging chapter headers
       doc: document postinstall steps
       README: remove sections present in manual
       doc: document src_prep variables
       doc: document RESTRICT
       spec: require cygwin-libtool
       autotools: use cross-libtoolize when cross-compiling if present
       cygport 0.10.10

-- 

Yaakov
Cygwin/X


CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
================================

If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:

http://cygwin.com/lists.html#subscribe-unsubscribe

If this does not work, then 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.

--
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-04-02  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02  3:56 Yaakov (Cygwin/X) [this message]
2012-04-02 11:03 ` Chris Sutcliffe
2012-04-02 19:15   ` Yaakov (Cygwin/X)

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=announce.4F7922A9.1090207@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).