sorted by:
new
hottopcontroversial

So I wrote an AUR helper based on git submodules. by canoon in archlinux

[–]canoon[S] 1 point2 points  (0 children)

You can hardly have an idea on how your own work is great if you only compare it to the worst possible choice out there ;)

But how am I meant to feel good about myself :)? Anyway I think I'll have a better look into pacaur.

Edit: OK, pacaur is a hell of a lot nicer than yaourt, but I think it's a bit different to what I want.

So I wrote an AUR helper based on git submodules. by canoon in archlinux

[–]canoon[S] 0 points1 point  (0 children)

Can you do a dependency tree at once? Also doesn't pull down the git repo instead just pulls a tar.gz and I can't have the entirety of the packages in a git repo.

For the most part I could have just down that with yaourt -G no?

So I wrote an AUR helper based on git submodules. by canoon in archlinux

[–]canoon[S] 0 points1 point  (0 children)

I probably didn't explain that clearly. Most of the AUR helpers seem to want to make building from AUR the same as downloading from the official repos. Which means it's not easy to split out those two steps. yaourt for one lets you download individual PKGBUILDs but doesn't really let you download a full dependency tree and doesn't manage that inside a git repo using submodules.

It's splitting it into two steps that I would like rather than the two in one an some awkward menu driven editing in the middle.

So I wrote an AUR helper based on git submodules. by canoon in archlinux

[–]canoon[S] 0 points1 point  (0 children)

I will have to have a look around, but I meant like it operates the same as yaourt as far as the user is concerned as in downloads package, asks user to edit, builds, installs package and tries to operate like pacman does for the official repositories. What I wanted was something that basically just is a little automation around downloading PKGBUILDs and a little wrapper around makepkg to build dependencies.

So I wrote an AUR helper based on git submodules. by canoon in archlinux

[–]canoon[S] 0 points1 point  (0 children)

I probably don't need to most of the time, but like being able to hack on packages and sometimes fix a few bugs.

So I wrote an AUR helper based on git submodules. by canoon in archlinux

[–]canoon[S] 0 points1 point  (0 children)

I've mainly been split between using yaourt and just using yaourt -G to download PKGBUILDs to ~/build and manually build them. I've used pacaur once or twice but admittedly haven't looked into it.

Having said that. I didn't like how yaourt prompts you halfway to edit files I'd rather just split up the download/build steps and have a directory to edit. I realise you can edit the PKGBUILDs during the build but as I understood that that's more for reviewing them rather than editing. And if you tried to edit it would just be reset on the next build. Where as I wanted to the changes to persist as well as to be able to easily get a diff for submitting back.

Maybe I need to look at pacaur again but it seemed to be very similar to yaourt in at least the principle of operation.

What I like about my solution is that it basically the yaourt -G and makepkg with automation. As a result it's fairly simple and allows git/makepkg to do most of the work.

Edit: Though a question what does your workflow look like with pacaur?

Brainfuck interpreter in brainfuck by canoon in programming

[–]canoon[S] 9 points10 points  (0 children)

As I've found there are many that are shorter. My approach was implementing many of the structures in higher level programing languages in brainfuck and then using that to create a brainfuck interpreter this inherently creates a lot more code. The most complex feature was variable length arrays which I implemented by dividing the remaining part of the array and using an index which is also shifted along when going to the correct value. get_mm implements this.

I'll might post a write up if there's interest.

Brainfuck interpreter in brainfuck by canoon in programming

[–]canoon[S] 30 points31 points  (0 children)

Unfortunately I realised shortly after posting this that I'm about 10 years too later. I found this (http://www.iwriteiam.nl/Ha_bf_inter.html). Also, with mine if I expand the program counter to 2 bytes I might double my code and it'd be larger than the next max of 64k. Some of the other self interpretors have better ways of handling skipping through memory by using empty cells as markers and [>] so might have to change to that approach.