On Friday, June 17, 2011 14:39:22 Kacper Kowalik wrote:
> W dniu 17.06.2011 18:41, Mike Frysinger pisze:
> > On Friday, June 17, 2011 05:01:10 Kacper Kowalik wrote:
> >> W dniu 17.06.2011 05:03, Mike Frysinger pisze:
> DEPEND="virtual/fortran"
>
> > RDEPEND="${DEPEND}"
> >>>
> >>> i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
W dniu 17.06.2011 18:41, Mike Frysinger pisze:
> On Friday, June 17, 2011 05:01:10 Kacper Kowalik wrote:
>> W dniu 17.06.2011 05:03, Mike Frysinger pisze:
DEPEND="virtual/fortran"
> RDEPEND="${DEPEND}"
>>>
>>> i'm not sure that RDEPEND is
On Friday, June 17, 2011 05:01:10 Kacper Kowalik wrote:
> W dniu 17.06.2011 05:03, Mike Frysinger pisze:
> >> DEPEND="virtual/fortran"
> >>
> >> > RDEPEND="${DEPEND}"
> >
> > i'm not sure that RDEPEND is correct. do all fortran compilers
> > additionally require the fortran compiler to be availa
On 17/06/11 11:01, Kacper Kowalik wrote:
> W dniu 17.06.2011 05:03, Mike Frysinger pisze:
>>> DEPEND="virtual/fortran"
RDEPEND="${DEPEND}"
>> i'm not sure that RDEPEND is correct. do all fortran compilers additionally
>> require the fortran compiler to be available at runtime ?
> They requir
W dniu 17.06.2011 05:03, Mike Frysinger pisze:
>> DEPEND="virtual/fortran"
>> > RDEPEND="${DEPEND}"
> i'm not sure that RDEPEND is correct. do all fortran compilers additionally
> require the fortran compiler to be available at runtime ?
They require fortran runtime library if they don't link it
On Friday, June 17, 2011 02:40:27 justin wrote:
> >> I wasn't aware of that. We are lacking any documentation about the
> >> proper documentation for manpages in all eclass writing guides.
> >
> > the syntax is fully documented in the utility that generates it. see the
> > awk in the eclass-manpa
>> I wasn't aware of that. We are lacking any documentation about the
>> proper documentation for manpages in all eclass writing guides.
>
> the syntax is fully documented in the utility that generates it. see the awk
> in the eclass-manpages filesdir.
>
This is not a proper way of documentati
On Friday, June 17, 2011 02:05:59 justin wrote:
> On 17/06/11 05:03, Mike Frysinger wrote:
> >> # @ECLASS: fortran-2.eclass
> >
> > i dont see fortran.eclass. what's with the "-2" ?
>
> There was a fortran eclass, which did completely different things. In
> order to not break an ancient package
Thanks again Mike for an extended review. Some replies on your comments
everything else is directly excepted.
On 17/06/11 05:03, Mike Frysinger wrote:
>> # @ECLASS: fortran-2.eclass
>
> i dont see fortran.eclass. what's with the "-2" ?
There was a fortran eclass, which did completely different
> # @ECLASS: fortran-2.eclass
i dont see fortran.eclass. what's with the "-2" ?
> @BLURB: Packages, which need a fortran compiler should inherit this eclass.
@BLURB: simplify fortran compiler management
>@DESCRIPTION:
> If you need a fortran compiler, inherit this eclass.
If you need a fortra
hi,
After some discussion the eclass evolved and is ready for the next round
of discussion.
justin
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
# Author Justin Lecher
# Test functions provided by Sebastien Fabbro and Kac
11 matches
Mail list logo
