Folder binary-i386 not created in apt repository

[ringods]

swaddle fails with this output:

/usr/bin/swaddle: 21686: cd: can't cd to /pipeline/source/target/download/apt/dists/rq-web-api-elx/multiverse/binary-i386

Output is 13MB and quite hard to get into a Gist. Other option

Side-question: can the creation of the apt repository be disabled? I only need a single package and I use deb-s3 to upload.

[raphaelcohn]

Try this release; I think I fixed this.

[raphaelcohn]

At the moment the apt repository is always created. It's swaddle's raison d'etre. It repositories are also intended to be versioned using git, because we needed a solution that produced a suite of packages that was consistent, not just one (a much better form of deb-marshal), and could be rolled back or forth and audited (indeed, when I created that bad package a while back, I used git to recover). Indeed, it's a primary reason to use swaddle. It also produces superb repositories, with every single optional feature enabled. Instead of using deb-s3, with swaddle, you'd just use rsync.

[ringods]

As you mentioned in #27, using the swaddle_apt architectures setting to amd64 only, already works for me. I'm going to build a new Docker CI build image including the latest swaddle and my pending project changes (folder structure) to see if everything falls into place.

🍻

[raphaelcohn]

I've taken a look and if you want to disable repository creation then it is possible by changing the code in swaddle_build(). Essentially, we'd need a global configuration setting that defaulted to apt, yum and files but could be changed. I'm happy to take a look at this on Monday.

[ringods]

👍

[raphaelcohn]

If I write the code would you do a PR for the README when I'm done? I think you'd produce something more useful from an user's perspective (;-)

[ringods]

Definitely!

[raphaelcohn]

Signing off for tonight. 4am start tomorrow.