1 |
On Sun, Jun 26, 2011 at 05:49:17AM +0200, Sebastian Pipping wrote: |
2 |
> On 06/26/2011 05:36 AM, William Hubbs wrote: |
3 |
> > That is already done if you use "git archive" to generate the archive |
4 |
> > and use the tags in the git repository along with that. For an example, |
5 |
> > look at openrc's git repository. |
6 |
> |
7 |
> I'm aware of git archive - it does not support handling of generated |
8 |
> files afaik. |
9 |
|
10 |
That's correct, everything has to be in the repository if you use it. |
11 |
The advantage of doing it that way is that anyone can come along |
12 |
whenever they want to and generate a tarball that exactly matches the |
13 |
one we generate at release time. Doing it the other way, they can't. |
14 |
|
15 |
That is why I think we should make asciidoc an RDEPEND in the ebuilds |
16 |
and set up the makefile so that the user generates the content if we |
17 |
stick with using asciidoc. |
18 |
|
19 |
> >>> I see two ways around this: We can either make asciidoc a build time |
20 |
> >>> dependency so that the user can use something like "make manpage" to |
21 |
> >>> generate the manpage |
22 |
> >> |
23 |
> >> That adds quite some load on indirect dependencies for more or less |
24 |
> >> nothing, as seen with Matt earlier. |
25 |
> > |
26 |
> > That is exactly why I prefer the other option I mention below. |
27 |
> |
28 |
> Alright. On the other hand without dependencies you get nowhere: either |
29 |
> you don#t have features or you build every wheel yourself. |
30 |
|
31 |
I'm not quite sure what you mean here. |
32 |
|
33 |
> >>> or we can go back to the manpage that is in the git |
34 |
> >>> repository. |
35 |
> >> |
36 |
> >> Do I have to list reasons against this option? |
37 |
> > |
38 |
> > I think it would be helpful if you did since you did the conversion |
39 |
> > without discussing it with the rest of the team first. |
40 |
> |
41 |
> Peter Volkov voted for it, Peter Stuge said the list was rather silent. |
42 |
> So I went for it. The migration in genkernel was of great help. I see |
43 |
> your apology in your other mail now, accepting. |
44 |
> |
45 |
> Benefits of the current Asciidoc approach: |
46 |
> |
47 |
> - No need to write *roff manually. |
48 |
|
49 |
I'll give you this one. :-) |
50 |
|
51 |
> Plus Asciidoc syntax is more readable. |
52 |
|
53 |
You can use man ./catalyst.1 to read the man page. |
54 |
|
55 |
> |
56 |
> - Man page keeps itself in sync on |
57 |
> |
58 |
> - list of subarches |
59 |
> |
60 |
> - version of catalyst |
61 |
> |
62 |
> - Option to make XHTML from the same source |
63 |
|
64 |
The cons of the new approach, as I see it, are: |
65 |
|
66 |
* auto generated content in tarballs makes it impossible to create the |
67 |
exact same tarball twice. |
68 |
* Now we need to have a build time dependency, at least for the live |
69 |
ebuild, which pulls in about 34mb of downloads just to build the man |
70 |
page. |
71 |
|
72 |
Since we are just talking about a man page, imho this is a lot of bloat |
73 |
for very little gain. |
74 |
|
75 |
William |