Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Gentoo Development (http://www.linux-archive.org/gentoo-development/)
-   -   gentoo-x86 commit in sci-astronomy/kapteyn: metadata.xml ChangeLog kapteyn-1.9.2.ebuild) (http://www.linux-archive.org/gentoo-development/398817-gentoo-x86-commit-sci-astronomy-kapteyn-metadata-xml-changelog-kapteyn-1-9-2-ebuild.html)

Jeremy Olexa 07-13-2010 07:32 PM

gentoo-x86 commit in sci-astronomy/kapteyn: metadata.xml ChangeLog kapteyn-1.9.2.ebuild)
 
On Tue, 13 Jul 2010 19:25:51 +0000 (UTC), "Kacper Kowalik (xarthisius)"
<xarthisius@gentoo.org> wrote:

> if use doc; then
> insinto /usr/share/doc/${PF}
> doins doc/*.pdf || die

An open question to all:

Should we be hiding pdf's behind USE=doc?? I've seen it here and there
as of late. I thought USE=doc was for compiling docs and/or pulling in
extra deps to build docs.

Thanks,
Jeremy

"Paweł Hajdan, Jr." 07-13-2010 07:43 PM

gentoo-x86 commit in sci-astronomy/kapteyn: metadata.xml ChangeLog kapteyn-1.9.2.ebuild)
 
On 7/13/10 12:32 PM, Jeremy Olexa wrote:
> On Tue, 13 Jul 2010 19:25:51 +0000 (UTC), "Kacper Kowalik (xarthisius)"
> <xarthisius@gentoo.org> wrote:
>
>> if use doc; then
>> insinto /usr/share/doc/${PF}
>> doins doc/*.pdf || die
>
> An open question to all:
>
> Should we be hiding pdf's behind USE=doc?? I've seen it here and there
> as of late. I thought USE=doc was for compiling docs and/or pulling in
> extra deps to build docs.

In my opinion we're never going to have 100% consistency here. I'd say
let everybody implement it in a way one thinks is the best.

The description of the flag is "Adds extra documentation (API, Javadoc,
etc)". So if something is an extra documentation, it seems to be fine to
"hide" it behind USE=doc.

And I'd prefer to keep the meaning of "extra documentation" flexible and
open to interpretation, just because there is no obvious benefit to aim
for 100% consistency here, and overstandardization would be bad.

Paweł

Steve Dibb 07-13-2010 07:43 PM

gentoo-x86 commit in sci-astronomy/kapteyn: metadata.xml ChangeLog kapteyn-1.9.2.ebuild)
 
On 07/13/2010 01:32 PM, Jeremy Olexa wrote:

On Tue, 13 Jul 2010 19:25:51 +0000 (UTC), "Kacper Kowalik (xarthisius)"
<xarthisius@gentoo.org> wrote:



if use doc; then
insinto /usr/share/doc/${PF}
doins doc/*.pdf || die


An open question to all:

Should we be hiding pdf's behind USE=doc?? I've seen it here and there
as of late. I thought USE=doc was for compiling docs and/or pulling in
extra deps to build docs.

I've seen it used sometimes where the docs themselves are really large,
and/or require a separate SRC_URI download as well.


But yah, makes most sense when you need it to change build deps and
actually do something.


Steve

Jeremy Olexa 07-13-2010 08:04 PM

gentoo-x86 commit in sci-astronomy/kapteyn: metadata.xml ChangeLog kapteyn-1.9.2.ebuild)
 
On Tue, 13 Jul 2010 12:43:17 -0700, "Paweł Hajdan, Jr."
<phajdan.jr@gentoo.org> wrote:
> On 7/13/10 12:32 PM, Jeremy Olexa wrote:
>> On Tue, 13 Jul 2010 19:25:51 +0000 (UTC), "Kacper Kowalik (xarthisius)"
>> <xarthisius@gentoo.org> wrote:
>>
>>> if use doc; then
>>> insinto /usr/share/doc/${PF}
>>> doins doc/*.pdf || die
>>
>> An open question to all:
>>
>> Should we be hiding pdf's behind USE=doc?? I've seen it here and there
>> as of late. I thought USE=doc was for compiling docs and/or pulling in
>> extra deps to build docs.
>
> In my opinion we're never going to have 100% consistency here. I'd say
> let everybody implement it in a way one thinks is the best.

I will highly disagree with this statement. If *WE* are not consistent,
how do the users of the distro know what to expect? Why does this USE
flag have a different standard then the rest?

> The description of the flag is "Adds extra documentation (API, Javadoc,
> etc)". So if something is an extra documentation, it seems to be fine to
> "hide" it behind USE=doc.
>
> And I'd prefer to keep the meaning of "extra documentation" flexible and
> open to interpretation, just because there is no obvious benefit to aim
> for 100% consistency here, and overstandardization would be bad.

No obvious benefit besides being consistent to our userbase. Do our
users expect non-consistent USE flags? That sounds bad to me. Sadly, I
think this is a subject that we will never get a consensus on. Maybe
the
description should be changed to:

global:doc: Adds extra documentation (API, Javadoc, PDFs at
maintainer's discretion, etc)

-Jeremy

Kacper Kowalik 07-13-2010 08:30 PM

gentoo-x86 commit in sci-astronomy/kapteyn: metadata.xml ChangeLog kapteyn-1.9.2.ebuild)
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

W dniu 13.07.2010 22:04, Jeremy Olexa pisze:
> global:doc: Adds extra documentation (API, Javadoc, PDFs at
> maintainer's discretion, etc)
I think you missed "API" here. I don't really see the difference
between bunch of html files and one 8Mb pdf file. In most cases the
former are not build either, yet they are "doc" flag dependent.
Cheers,
Kacper Kowalik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iJwEAQECAAYFAkw8zPYACgkQIiMqcbOVdxTQogP+Ki4Ik61GfT 0zsRJ/bKN86pnR
PGQehSEapEoyG0qcUUbc4kXKqYxsO6oyVpTMNTZq3vCLPyALjM 3/oOlcP9/Rh3Lh
t6iw7jgA29iz+pF204WZ4ACPG+74libf0hZf6Gw2npgMA6MWPR SpRmAv8rBIoOrZ
nS4FZFtmOxyaOhmnyAI=
=ro1B
-----END PGP SIGNATURE-----


All times are GMT. The time now is 09:57 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.