Currently, if the build server downloads a file that fails the md5sum check
for some reason (perhaps interrupted download, etc), the file is never deleted
so the build can not succeed until someone manually deletes the bad file. This
change deletes any file that is a remote source file / package that fails the
md5sum check. The subsequent rebuild will then be forced to download the file
again.
due to unintialized and non-local variable the tracing of deps
didnt work as expected when dependencies was provided by the apkbuild
itself. (libgcc ended up depending on libgcj which depended on binutils)
This subcommand verifies if upstream sources still exists and echoes
an error if it does not.
This is supposed to be used from a script that checks the validity
of source regularily.
'saveas-*://' URI support has been created for use with the source= line of
APKBUILD files.
It allows for a remote source file to be saved with an arbitrary filename. This
is useful in situations where the last component of the URI is not the preferred
filename.
Here's how it works. Say we have the following URI:
http://oss.example.org/?get=software&ver=1.0
Both Busybox Wget and GNU Wget will save this with the filename:
?get=software&ver=1.0
To get around this, we could use cURL to save the file using the filename in the
HTTP response headers:
$ curl -JO "http://oss.example.org/?get=software&ver=1.0"
Or we could use this 'saveas' hack. Essentially, the original URI is converted
to read:
saveas-http://oss.example.org/?get=software&ver=1.0/software-1.0.tar.gz
In the download process, the 'saveas-' portion is removed, and the file is
downloaded from the original URI, but is saved with the filename being the last
component of the URI. In this case, it will be saved as 'software-1.0.tar.gz'.
It is designed so that it works with any protocol supported by abuild.
For example:
saveas-ftp://oss.example.org/?get=software&ver=1.0/software-1.0.tar.gz
Check it out and let me know what you think.
Thanks,
Matt
Some .so files have a rpath where to look for the needed .so. When tracing
package dependencies we also have a look there.
This should fix problem when the .so is not in standard location, /usr/lib
or /lib. (for example freeradius plugins)
While here we also reorganize things so we only call apk info --who-owns
once for each package instead of once for each needed .so. This should
speed up things when there are many needed .so files.
