On 30/09/17 13:24 +0200, Kevin Kofler wrote:
adel...@zegrapher.com wrote:
Yea well, since I used the convention of including libs only in the .h I
didn't do so. But yes you're right! I will update that.
Well, that convention doesn't make sense to begin with.
You should only #include in the .h
adel...@zegrapher.com wrote:
> Yea well, since I used the convention of including libs only in the .h I
> didn't do so. But yes you're right! I will update that.
Well, that convention doesn't make sense to begin with.
You should only #include in the .h file what you actually need to declare
your
On 28.09.2017 00:22, Kevin Kofler wrote:
adel...@zegrapher.com wrote:
and Boost for only one small function
Since I was curious, I looked for that function and found it in
polynomial.cpp. But why do you include the headers in polynomial.h? The
usage of Boost in Polynomial::translateX is an imp
adel...@zegrapher.com wrote:
> and Boost for only one small function
Since I was curious, I looked for that function and found it in
polynomial.cpp. But why do you include the headers in polynomial.h? The
usage of Boost in Polynomial::translateX is an implementation detail and so
the headers sh
/*Jason L Tibbitts Iii*/ wrote on Tue, 26 Sep 2017 22:49:18 -0500:
"HV" == Hedayat Vatankhah writes:
HV> I'd say to stick with upstream naming, which is the Fedora
HV> way. Changing the names to lower case is a must in Debian, they
HV> simply don't allow upper case letters to be in package nam
On 27 Sep 2017 04:50, "Jason L Tibbitts III" wrote:
> "HV" == Hedayat Vatankhah writes:
HV> I'd say to stick with upstream naming, which is the Fedora
HV> way. Changing the names to lower case is a must in Debian, they
HV> simply don't allow upper case letters to be in package names. The
HV
> "HV" == Hedayat Vatankhah writes:
HV> I'd say to stick with upstream naming, which is the Fedora
HV> way. Changing the names to lower case is a must in Debian, they
HV> simply don't allow upper case letters to be in package names. The
HV> developer clearly prefers ZeGrapher, so I think acco
/*Samuel Rakitničan*/ wrote on Mon, 25 Sep 2017 23:15:25 -:
Here it is:
https://copr.fedorainfracloud.org/coprs/srakitnican/default/build/607839/
Still not sure about naming issue, package wants to name files ZeGrapher, I
called the package zegrapher, debian maintainers go a step further
/*Samuel Rakitničan*/ wrote on Mon, 25 Sep 2017 23:15:25 -:
Here it is:
https://copr.fedorainfracloud.org/coprs/srakitnican/default/build/607839/
Still not sure about naming issue, package wants to name files ZeGrapher, I
called the package zegrapher, debian maintainers go a step further
On Mon, Sep 25, 2017 at 11:15:25PM -, Samuel Rakitničan wrote:
> Here it is:
> https://copr.fedorainfracloud.org/coprs/srakitnican/default/build/607839/
>
> Still not sure about naming issue, package wants to name files ZeGrapher, I
> called the package zegrapher, debian maintainers go a ste
On lundi 25 septembre 2017 21:27:34 CEST adel...@zegrapher.com wrote:
> Hello!
>
> I am contacting you here because I have found this thread [1] on
> askfedora, I hope I am not bothering by sending this mail (in the wrong
> list). If I am doing so, please accept my excuses in advance...
>
> So! I
Here it is:
https://copr.fedorainfracloud.org/coprs/srakitnican/default/build/607839/
Still not sure about naming issue, package wants to name files ZeGrapher, I
called the package zegrapher, debian maintainers go a step further and call
package files zegrapher also.
TODO: AppStream metadata
I
12 matches
Mail list logo
