On Sat, Jun 25, 2011 at 11:14 PM, Sebastian Pipping <[email protected]> wrote: > On 06/26/2011 04:49 AM, William Hubbs wrote: >> No, we can't have the manpage pre-rendered in the tarball, because that >> makes the tarball different every time it is created since the >> date/timestamps in the archive will be different. In other words, it is >> not possible for anyone to ever reproduce the exact same tarball that we >> produce. > > The varience in timestamp has been no problem for other projects > including genkernel. If all that varies is the time stamp and it > matters to you, it would be easy to add a section to the Makefile > setting the timestamp to a hardcoded value. > > >> I see two ways around this: We can either make asciidoc a build time >> dependency so that the user can use something like "make manpage" to >> generate the manpage > > That adds quite some load on indirect dependencies for more or less > nothing, as seen with Matt earlier.
For the live ebuild, I don't see any problem with this. I think we just want to avoid having to install asciidoc for the released catalyst versions. >> or we can go back to the manpage that is in the git >> repository. > > Do I have to list reasons against this option? Yeah, this option is really distasteful. I think the best solution is to simply hack the timestamp on the generated files or something similar. We definitely don't want `emerge =catalyst-2*` to require asciidoc and all its indirect dependencies for a single man page, and we definitely don't want to check-in generated files to git for a variety of reasons. Matt
