Package Details: nand2tetris 2.6-4

Git Clone URL: (read-only, click to copy)
Package Base: nand2tetris
Description: Software suite accompanying Nand2Tetris course.
Upstream URL:
Licenses: GPL
Submitter: chadvoegele
Maintainer: chadvoegele
Last Packager: chadvoegele
Votes: 6
Popularity: 0.000141
First Submitted: 2014-01-04 19:46
Last Updated: 2020-10-24 02:53

Required by (0)

Sources (9)

Latest Comments

1 2 3 Next › Last »

abrahammurciano commented on 2020-10-24 19:16

@chadvoegele idk about @mar04, but my "workflow" is to use yay. So every so often I upgrade my machine with yay, and if you update the pkgrel, it tries to install nand2tetris again because it sees that the pkgrel is newer. So I just tried to upgrade and I got the "error" telling me to download from Therefore it didn't upgrade that package, and nand2tetris will always have a pending update until I download the source again and place it in srcdir. Please bump down the pkgrel, or everyone with this package will always see there is a pending update, even though they have no need to install it again.

chadvoegele commented on 2020-10-24 12:06

@mar04, sure. Curious what is your workflow? I've always used AUR manually, so would have just not updated in this case.

mar04 commented on 2020-10-24 10:20

Please don't bump pkgrel for such trivial changes - there is no need for existing users to update.

chadvoegele commented on 2020-10-24 02:54

Thanks, made your suggested update.

abrahammurciano commented on 2020-10-23 14:19

Amazing, thank you. There is one more thing you might consider. The message printed says to download the "source" however, if you go to the nand2tetris site, there's the standard zip file to download, and further down at the bottom you can also download the actual source. This may confuse users. At first I thought the PKGBUILD was requesting the actual source, but when I checked the PLKGBUILD I saw it was expecting a file with the name Perhaps we can make this clearer in the message by saying something like "... download the file from and move it into $srcdir"

chadvoegele commented on 2020-10-23 03:14

Hi abrahammurciano, thanks for the suggestions! I changed the upstream url to just the homepage. That should be more robust to url changes. As you recommended, I changed to $srcdir.

abrahammurciano commented on 2020-10-22 17:43

Please consider using the gdrive tool to download the zip instead of telling the user to do it. And if that is infeasible, at least tell the user precisely (absolute path, eg echo $srcdir) where to put the zip file.

Also, the zip file is outdated. Please update that.

chadvoegele commented on 2018-12-28 22:35

Thanks for the report!

I reworked the PKGBUILD to have users download the source manually via their browser. I'm not sure there is a better solution.

Others have asked in the forums [1] [2] about Google drive links and the advice seems to be to host somewhere else, either by asking upstream or cross-posting. Neither of those options seems feasible in this case.

[1] [2]

cweagans commented on 2018-12-26 00:25

==> Retrieving sources...
  -> Downloading 1KcFPj8KQ_QAHheFmLCqs5iqC_0NCndvs...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 403 
==> ERROR: Failure while downloading*/1KcFPj8KQ_QAHheFmLCqs5iqC_0NCndvs

It looks like that Drive link is having some issues already. Maybe it would be a good idea to expect the user to handle creating ~/Downloads/, and then have the pkgbuild use that instead? does this and it works pretty well.

craftyguy commented on 2018-11-25 22:47

Looks good, I was able to build it!

Yea, the google drive direct link might cause problems for you in the future if/when it changes arbitrarily..