On 07/03/2014 03:15 PM, Dennis Gilmore wrote: >> For example, when using the default URL path rpkg attempts to >> download the following file: >> https://git.centos.org/sources/a2ps/SOURCES/a2ps-4.14.tar.gz/365abbbe4b7128bf70dad16d06e23c5701874852/SOURCES/a2ps-4.14.tar.gz > >> The path I wish to set for rpkg to use is: >> https://git.centos.org/sources/a2ps/c7/365abbbe4b7128bf70dad16d06e23c5701874852 > > ewww, seriously eww. the tooling would need to rename the file it gets > to the name in the spec file. this I think doesn't belong in rpkg,
yes, so rather than using a curl -O, you get to give it a name to write to - a name that maps to sanity in the source repos, and does the sha validation without needing to waste time doing it down the road, and a process that allows far better and more effecient duplication checks on the cache side. tell me why we'd want to change to lose all that functionality ? I'm getting assurance on code retreval to match code checkin, for free. > whatever tooling centos people come up with will have to replace rpkgs > function with its own version. I would strongly advocate for centos to > rethink how they are doing it and follow the standard convention. 'standard convention'... which is exactly what ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc -- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
