From: "Samuli Suominen (ssuominen)" <ssuominen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in x11-libs/fltk: fltk-1.1.9.ebuild Manifest
Date: Mon, 21 Mar 2011 16:48:25 +0000 (UTC) [thread overview]
Message-ID: <20110321164825.6DBE820054@flycatcher.gentoo.org> (raw)
ssuominen 11/03/21 16:48:25
Modified: Manifest
Removed: fltk-1.1.9.ebuild
Log:
old
(Portage version: 2.2.0_alpha28/cvs/Linux x86_64)
Revision Changes Path
1.189 x11-libs/fltk/Manifest
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/fltk/Manifest?rev=1.189&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/fltk/Manifest?rev=1.189&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/x11-libs/fltk/Manifest?r1=1.188&r2=1.189
Index: Manifest
===================================================================
RCS file: /var/cvsroot/gentoo-x86/x11-libs/fltk/Manifest,v
retrieving revision 1.188
retrieving revision 1.189
diff -u -r1.188 -r1.189
--- Manifest 20 Mar 2011 19:52:17 -0000 1.188
+++ Manifest 21 Mar 2011 16:48:25 -0000 1.189
@@ -1,6 +1,3 @@
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA1
-
AUX FLTKConfig.cmake 1217 RMD160 5dd0903afe144b63c17dfb50b318b9d994787697 SHA1 2b09f60de6ae8ba1c1d625240e734b0413e643ca SHA256 cefffd18b6320c83aa546c953790b3dab9e4b99c0f43633b6994bdb7db69877e
AUX fltk-1.1.7-amd64.patch 2433 RMD160 fb625474ff36b75a35394862b45653c30c6728e5 SHA1 f28f8a87f62e006a7544ff029d62e89a8d87a39c SHA256 25619bc596b59824d4e5737b0796f2e79ea6f2ca1dc4aabaa69702be1bf80e10
AUX fltk-1.1.7-as-needed.patch 4767 RMD160 5f2b64450cd2347b9357799f5ddb32084e913b7a SHA1 90e819e5f1dd577a33e818dab4ef24f623bbf06d SHA256 c19b73f1fd75d1a38df958577c5288f6b10cad64e9fb7b54e6b0ffef57f88772
@@ -32,16 +29,8 @@
EBUILD fltk-1.1.10-r1.ebuild 3833 RMD160 c7effc1b0b783fbe62d46251b6a559071e4837ee SHA1 a7f1e1da751bed11e16594084cc84e2c31df1bb8 SHA256 bc20a55bd762921f0d8e089927e144a039ac011212906ce54420646715d1539e
EBUILD fltk-1.1.9-r1.ebuild 3611 RMD160 924652d65bd24295c08589744a590521af02e34a SHA1 b5d7d636b182874c1b6cad9bd882d40dd2ebc8f1 SHA256 88a3f8781d0d9459f3f9474bd51bc48a5f40f93662e00f4722599b09e086fa4c
EBUILD fltk-1.1.9-r2.ebuild 3663 RMD160 d65a88185f486a3a9f1239014354a7678ec0741d SHA1 bc358ac9a4d62bdeabe4e36b58afb71da53ec404 SHA256 97db5986301cc5a767de3655b9eaae31310b9f9238371e79a69fdc18cbe86564
-EBUILD fltk-1.1.9.ebuild 3503 RMD160 cbc9d3f31b1b1f0753123ea249d1619d0ccc9d5f SHA1 3b7b9f08800aab973baf9a0d50da6800fcf118c9 SHA256 f8e70040854225ea9cf99ae28d0d70b74d3246e91ba1ef04cf77a324592f5b6b
EBUILD fltk-1.3.0_rc3-r1.ebuild 3801 RMD160 b79a72d6cdd3ab00468de935496980d87497c2e4 SHA1 4799397a5be7e44367f312cefe6960c92e9f6047 SHA256 5abad55f9ebbb71d62ade244be8ffb71718be2311e4ca85741e8eed7a3295124
EBUILD fltk-2.0_pre6970-r1.ebuild 2643 RMD160 3f2586e399d6d8d528458de6290474c6d8f71745 SHA1 231219d7b2a21b5f19fae8c1381add0c3d44b61c SHA256 30bcdb648e978978ea3f6e183efac6f02f008fbe345cde19c3257ad95e50a2d6
EBUILD fltk-2.0_pre6970.ebuild 2499 RMD160 473e33748481ede77d977856375059b48994667e SHA1 d4b27ae1b48a9573104cd62ca106ad2ff9359acb SHA256 9151a4aaf72a4d22301cd16c8cf06461410a5121939162347da14c3106c4bffd
MISC ChangeLog 24126 RMD160 5187faf8fbe69f350b56da7083e02ea7684417db SHA1 9613ee1aec13fd6d901ea4e4eb0b68ad5d1b0786 SHA256 f74caa23f8b1b14397e7a980e817ec3ce101c6474a25d0806016559e00b14e8a
MISC metadata.xml 657 RMD160 24969ef07785738fc34d10c79dcc854d2a895ec3 SHA1 8afd06ddc3b01090acf0333f2ac41fc4a692f504 SHA256 f37b711686e55a32ab4a1e050ee6e98fbfd7e6d7839c53926b6103fff61c44b1
------BEGIN PGP SIGNATURE-----
-Version: GnuPG v2.0.17 (GNU/Linux)
-
-iEYEARECAAYFAk2GWvEACgkQgAnW8HDreRZZTgCg0poGONR2P6NLVr6/A5ZM2jT0
-8+QAnAjOV8V684VES8aUS9IJK2K9krCW
-=zI2S
------END PGP SIGNATURE-----
reply other threads:[~2011-03-21 16:48 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=20110321164825.6DBE820054@flycatcher.gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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