Checksums don't need any special treatment with downloadfilename parameter.
On Mon, May 7, 2018 at 5:48 PM, Trevor Woerner <[email protected]> wrote: > Hi Martin, > > On Mon 2018-05-07 @ 05:33:26 PM, Martin Jansa wrote: > > There is already a fix for this, see: > > http://lists.openembedded.org/pipermail/openembedded-core/ > 2018-May/150423.html > > Oops, I should have checked, sorry! > > > Using github archives is even worse as they are regenerated from time to > > time. > > Crazy! But good to know. > > > Also when you really want to use v${PV}.tar.gz archive, then > > use downloadfilename parameter to fetch it with some more meaningful > > filename and to prevent possible conflicts with other badly named > tarballs. > > Oh, I see, in one's own DL_DIR. So (not that this patch is relevant > anymore) > instead of: > > -SRC_URI = "http://www.efficios.com/files/babeltrace/babeltrace-${ > PV}.tar.bz2 \ > -" > +SRC_URI = "https://github.com/efficios/ > babeltrace/archive/v${PV}.tar.gz" > > better: > > -SRC_URI = "http://www.efficios.com/files/babeltrace/babeltrace-${ > PV}.tar.bz2 \ > -" > +SRC_URI = "https://github.com/efficios/ > babeltrace/archive/v${PV}.tar.gz;downloadfilename=babeltrace-v${PV}.tar.gz > " > > In this case, would the checksums need a tweak too, or do they know to look > for the downloadfilename file name? >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
