[Slackbuilds-users] nvidia-driver.info missing 64bit file info
Greg' Ar Tourter
artourter at gmail.com
Mon Jul 15 19:31:58 UTC 2013
Well looking through the repository, the nvidia-driver (and
avr8-gnu-toolchain, but that's only for the pdf manual) packages are the
only ones with files in common. So asking to download both version seems
rather a waste of bandwitdh
Moreover, for some packages (ucsc-blat, p4, p4v ), the source file name is
the same for 32 and 64 bit version but are downloaded from different
locations and have different checksum. in these case, wget with append .1
to the second one and therefore making the slackbuild use the 32bit version
instead.(unless sbopkg instruct wget to overwrites the previous version
which again would be a waste of bandwidth)
just my 2p worth though.
On 15 July 2013 18:56, Robby Workman <rworkman at slackbuilds.org> wrote:
> On Mon, 15 Jul 2013 18:52:20 +0100
> "Greg' Ar Tourter" <artourter at gmail.com> wrote:
> > All the recently released/updated nvidia*-driver.info file are
> > missing the source files and associated md5sum for the 64bit version.
> > There are indeed common to bot the 32 and 64 bit version but need to
> > be specified for both. Currently sbopkg fails because it isn't
> > downloading the tar.xz files on 64bit machines since only the .run
> > file is specified.
> Hrm, my fault, but I'm not convinced that sbopkg is DTRT.
> I'm going to CC the sbopkg list to solicit feedback, but it's my point
> of view that sbopkg should *always* pull the things specified in
> $DOWNLOAD, and if on x86_64, pull the things specified in
> $DOWNLOAD_x86_64. Unless my memory is failing me, that is how we
> envisioned things working when we added the *_x86_64 variables to
> the .info file.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SlackBuilds-users