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