From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mo6-p00-ob.smtp.rzone.de ([2a01:238:20a:202:5300::4]) by metis.ext.pengutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1aihRf-0001fI-Vl for ptxdist@pengutronix.de; Wed, 23 Mar 2016 12:59:28 +0100 Received: from [127.0.0.1] ([109.199.162.184]) by smtp.strato.de (RZmta 37.22 AUTH) with ESMTPSA id 3074e0s2NBwwIkA (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Wed, 23 Mar 2016 12:58:58 +0100 (CET) From: =?UTF-8?Q?Hubert_M=c3=b6=c3=9flein?= Message-ID: <56F284F6.6080908@megatec.info> Date: Wed, 23 Mar 2016 12:58:46 +0100 MIME-Version: 1.0 Subject: [ptxdist] ipk dependency by version List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============0451439047==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============0451439047== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gQPomrGMH6X87eSnXoB7bhSKB3UcVoa8K" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gQPomrGMH6X87eSnXoB7bhSKB3UcVoa8K Content-Type: multipart/mixed; boundary="8DTotXi4c2rrxsHR2sVwaVMS65H2M6LQC" From: =?UTF-8?Q?Hubert_M=c3=b6=c3=9flein?= To: ptxdist@pengutronix.de Message-ID: <56F284F6.6080908@megatec.info> Subject: ipk dependency by version --8DTotXi4c2rrxsHR2sVwaVMS65H2M6LQC Content-Type: multipart/mixed; boundary="------------050401060203010002000208" This is a multi-part message in MIME format. --------------050401060203010002000208 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, I need to insert a dependency by version number, as a packet needs a lib from a certain version or above. For the 1st I manually changed the control file of the ipk archive and changed the line Depends: mylib to Depends: mylib (>=3D1.02) That ensures that the ipk will only update if the mylib has actualised before to 1.02 at least. Now my question: How can I automatically achieve with ptxdist to build the ipk control file automatically with the version information? I want to avoid a future build of the application ipk, where I forget to manually include the version information. Thanks in advance Hubert --=20 megatec electronic GmbH Dipl. Ing. Hubert Moesslein Lehenhammer 14 92268 Etzelwang @ : h.moesslein@megatec.info www.megatec.info Gesch=C3=A4ftsf=C3=BChrer: Dipl. Ing. Gerhard Pirner Registergericht Amberg HRB 837 --------------050401060203010002000208 Content-Type: text/x-vcard; charset=utf-8; name="msl.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="msl.vcf" begin:vcard fn;quoted-printable:Hubert M=3DC3=3DB6=3DC3=3D9Flein n;quoted-printable:M=3DC3=3DB6=3DC3=3D9Flein;Hubert email;internet:msl@megatec.info tel;work:09154/9497-0 tel;fax:09154/9497-10 x-mozilla-html:FALSE version:2.1 end:vcard --------------050401060203010002000208-- --8DTotXi4c2rrxsHR2sVwaVMS65H2M6LQC-- --gQPomrGMH6X87eSnXoB7bhSKB3UcVoa8K Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJW8oT7AAoJEBp9F1GNCrVElU8H/iGnX4yGV8RfB1PQAx/C/g/L 1RksTzRHh5OO3OCJ9cy7KqcfbK0llSryjCv2e1shYKRDO4o4i+nDkI9jw6YZX/KD fCBlLTmP0toh44BJq2zjR2PqbBQA3+xfMkptGyJ+o70EEy7UDOFfGn4/7q2iGSfk hLculYDAZAgdPt7hpFfsVuXqsxhS5BLAcwB6hfgpseM9a0KEanqIJ2/FGz63/Sta 8w2XNeicNM+Vx+myEKTCCke2vhI2bxv6un1FN+CU2x9U9Ay38yTXmH35VgOWgObo MEyx/4+yHBO/LnvO7Q3NotFyfYYj4WvUF+pOWQd/WHJOZFoi8F3hvWufVyBFKmo= =Sp3x -----END PGP SIGNATURE----- --gQPomrGMH6X87eSnXoB7bhSKB3UcVoa8K-- --===============0451439047== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0451439047==--