1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
I wonder if it would make any sense to take the effort to convert |
5 |
markdown docs to html format before installing them. |
6 |
|
7 |
I see two possibilities: |
8 |
|
9 |
1. Create one or two eutils functions like |
10 |
"domd": will go through all viable implementations like |
11 |
markdown/markdown_py/Markdown.pl, convert the file and dohtml it. Is |
12 |
no impelementation installed on the system it will fall back to plain |
13 |
dodoc. |
14 |
Optionally we could provide "md_depend" (like DEPEND="$(md_depend)") |
15 |
to ensure that at least one implementation is present (might be useful |
16 |
for very huge docs that are easier to read as html). |
17 |
|
18 |
2. Introduce something like virtual/markdown... unfortunately the |
19 |
"markdown" name is already reserved by app-text/discount, so I don't |
20 |
really know how that would work out. And the supported arguments might |
21 |
differ... |
22 |
|
23 |
This is low priority, so if this is going to take more then little |
24 |
work, I'll probably lose interest. |
25 |
-----BEGIN PGP SIGNATURE----- |
26 |
Version: GnuPG v2.0.20 (GNU/Linux) |
27 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
28 |
|
29 |
iQEcBAEBAgAGBQJSQdCtAAoJEFpvPKfnPDWzTAUH/iv42uJz9S1Ky0j6jSYYNlYo |
30 |
MGPdo6oQFMVHUOSBuC0tqz/k/sWnk32K3MYYoTfneVK907jMjGK+TLrdAy35nXjD |
31 |
PKDQeu3lZvA9Yd1RhDtKWAKOj32OJTvxtBakX4Q+RielBhgesIzfJVAYVAFGk/l7 |
32 |
igwpabGuKCz8xC13DSvvMScHSod9f/eGuHGcT/4TM5DuMXodWKHuqN9Smy02cPuL |
33 |
9AluDpmbRcummpyTiWjMgAvPEPhlowsg/DMSzd8Cz/eeeOJsZtIFF+fBQOGP5xHI |
34 |
eIW4SoRFGnBMB8lM35aEBoN7WlrvR6lKmQay/CVqN2a3H0Zyd8Zt1p66pkkx2So= |
35 |
=1R0w |
36 |
-----END PGP SIGNATURE----- |