| 1 |
version=3 |
| 2 |
|
| 3 |
# distributed.net's release scheme is a bit different than normal and what uscan |
| 4 |
# expects. A distributed.net version number consists of a major version, a |
| 5 |
# minor version and a build fraction. All of these are separated by dots (see |
| 6 |
# the upstream changelog for the details). distributed.net encodes only the |
| 7 |
# build fraction in the file name. The major and minor version numbers are |
| 8 |
# encoded in the name of the directory containing the files. uscan expect the |
| 9 |
# full version number to be encoded into the file name. While less than ideal |
| 10 |
# updates will have to be tracked using the build fraction only. This requires |
| 11 |
# the actual version number to be removed from the local version for processing. |
| 12 |
# |
| 13 |
# distributed.net's updates tend to be architecture specific. For example a new |
| 14 |
# release my include a new version for i386 and mips but nothing else. |
| 15 |
# Furthermore distributed.net supports a number of architectures that are not in |
| 16 |
# Debian. Therefore uscan needs to look for releases of architectures supported |
| 17 |
# by Debian only. Otherwise a new version for an architecture that is not in |
| 18 |
# Debian could trigger a new version of this package. |
| 19 |
|
| 20 |
opts=pasv,dversionmangle=s/^[0-9]\.[0-9]+\.// \ |
| 21 |
ftp://ftp.distributed.net/pub/dcti/v([\d\.]+)/dnetc([\da-z]+)-linux-(?:x86-elf-uclibc|amd64|ppc|armel|mips32el).tar.gz debian uupdate |