Alejandro R Mosteo

I understand the problem... > Could the lockfile be used for this? I think so, as the worst that can happen is that if the lockfile is deleted the build...

> Or maybe the local config file could be used here to log the latest build profile... Indeed, it seems even a better option.

Now I got a clear [answer](https://github.community/t5/How-to-use-Git-and-GitHub/Ensuring-identical-tarballs-from-releases/m-p/35808/highlight/true#M9217). For whatever reason they're keeping a escape clause open, so we should at least make a recommendation to generate your own tarball, and where...

> Should we consider generating the archives with alr publish and hosting them in the index repo or another repo? I don't think we can allow users to do so;...

OK, I had misunderstood you. [Here are the limits](https://help.github.com/en/github/managing-large-files/what-is-my-disk-quota): 100MB per file, 100GB per repo, but we enter the radar at 1GB. So, I don't think GitHub would look happily...

> So, `alr publish [index]` from within an alire project should put a tar.gz file at the index location, Actually the tarball should be put somewhere online, tarballs don't go...

> For nuget, there is a nuget.spec file that defines which files go into the nuget package file. That saves the system from having hardcoded ignore lists; I understand we...

Your tarball/zipball must contain a single folder (like the `apdf` you mention), name not important, that in turn contains your sources. > Does that mean with statements will need to...

Thanks for the report, Jesper.

As I see it, our current solution is a pure sandbox because everything needed is entirely in a workspace. Doing this would mean going out of that sandbox into another...