corelinux-develop — Developer centric mail list for CoreLinux++

Re: [Corelinux-develop] .changes and .dsc

[Christophe Prud'h. <pru...@MI...>]

>>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:

    Frank> Christophe, What is the signifigance of the files mentioned in the subject?  Are they
    Frank> needed to be part of the release?
they are needed if we want corelinux to be a part of
debian ! I was a debian developper in the past but due
to heavy work, I had to stop this activity. But now 
that I am working on projects with debian packages I can be one again
I have to sign some stuff etc. Otherwise they are not really needed. 

Debian has the most powerful tool to upgrade the system
you have a local database(built upon the .dsc) and there are 
some debian servers whole around the world which allow you
 to upgrade your local database and then upgrade the softwares. 
No other distribution has such an automatic tool
(they couldn't sell CDs with such a tool available :) )


regards
C.

Re: [Corelinux-develop] Front page

[Hans - D. <dul...@eg...>]

On Thu, 13 Jul 2000, Frank V. Castellucci wrote:

> Date: Thu, 13 Jul 2000 23:57:08 -0400
> From: Frank V. Castellucci <fr...@co...>
> Reply-To: cor...@li...
> To: CoreLinux Development <cor...@li...>
> Subject: [Corelinux-develop] Front page
> 
> Hans,
> 
> Ok with you if I add you to the web page as a player?
>

It is ok.
 
> 

-- 
Hans Dulimarta, Ph.D.             dulimart@[egr.msu.edu, computer.org]
Visiting Research Associate         http://www.egr.msu.edu/%7edulimart   
                           Ph: (517)432-7589  Fax2Email: (760)281-7691
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

Re: [Corelinux-develop] Re: PDF generation problem fixed.

[Hans - D. <dul...@eg...>]

On Thu, 13 Jul 2000, Christophe Prud'homme wrote:

> Date: Thu, 13 Jul 2000 17:15:11 -0500 (EST)
> From: Christophe Prud'homme <pru...@MI...>
> Reply-To: cor...@li...
> To: cor...@li...
> Subject: Re: [Corelinux-develop] Re: PDF generation problem fixed.
> 
>     Frank> Frank tests RPM packages (can't test debian because I don't have it)
>     the debian packages are working fine for me
> 
>     Frank> Figure 0.4.25 will go out by Saturday -0500 EST
> good :)
> 
> C.
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 

I'll finish up modifying some more .tex files under htdocs today.

-- 
Hans Dulimarta, Ph.D.             dulimart@[egr.msu.edu, computer.org]
Visiting Research Associate         http://www.egr.msu.edu/%7edulimart   
                           Ph: (517)432-7589  Fax2Email: (760)281-7691
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

[Corelinux-develop] Front page

[Frank V. C. <fr...@co...>]

Hans,

Ok with you if I add you to the web page as a player?

-- 
Frank V. Castellucci

[Corelinux-develop] .changes and .dsc

[Frank V. C. <fr...@co...>]

Christophe,
What is the signifigance of the files mentioned in the subject?
Are they needed to be part of the release?

-- 
Frank V. Castellucci

Re: [Corelinux-develop] Re: PDF generation problem fixed.

[Christophe Prud'h. <pru...@MI...>]

    Frank> Frank tests RPM packages (can't test debian because I don't have it)
    the debian packages are working fine for me

    Frank> Figure 0.4.25 will go out by Saturday -0500 EST
good :)

C.

Re: [Corelinux-develop] Re: PDF generation problem fixed.

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:

>     Hans> If you look at the cppstnd.tex document, you'll find something like "${}$Revision: 1.3
>     Hans> ${}$". This is a TeX trick which I learned from the comp.text.tex newsgroup to incorporate
>     Hans> RCS keyword in LaTeX documents.  The trick works for the .dvi, .ps. and .pdf output, but
>     Hans> not for the .html output.
> good
>     Hans> latex2html convert the empty equations "${}$" to pictures and we can see empty rectangles
>     Hans> on the browser. Later on, one of the TeX gurus, Don Arseneau, pointed me to rcs.sty. I
>     Hans> tried it and it worked well.  However, rcs.sty is not part of the tetex instalation
>     Hans> package.  How should we go about using this package? Should we put it under htdocs/tex
>     Hans> subdir or should we let the users install their own rcs.sty?
> you can put it in htdocs/tex
> this is the place for tex/latex2html related files
>
>     Hans> Another question: there are two date strings on the title. "May 8, 2000" and
>     Hans> "Documentation revised May 14, 2000". What are these dates? Which one can be generated by
>     Hans> RCS keyword $Date$?
> the first date is the date of creation
> the second dsate is the revision date
> the second must be changed
>
>     Hans> Once the issues are finalized I'll make another cvs commit.
> good
>
> where are we on the packages side Frank ? did you have the time to check the packages
> I put on corelinux.sourforge.net ?
> what is the schedule for the next release?

Hans puts files up
Frank tests RPM packages (can't test debian because I don't have it)
Frank Extracts and BVTs on compile farm
Frank Build tar.gz and docs

Figure 0.4.25 will go out by Saturday -0500 EST

>
>
> regards
> christophe
>
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

[Corelinux-develop] Re: PDF generation problem fixed.

[Christophe Prud'h. <pru...@MI...>]

    Hans> If you look at the cppstnd.tex document, you'll find something like "${}$Revision: 1.3
    Hans> ${}$". This is a TeX trick which I learned from the comp.text.tex newsgroup to incorporate
    Hans> RCS keyword in LaTeX documents.  The trick works for the .dvi, .ps. and .pdf output, but
    Hans> not for the .html output.
good
    Hans> latex2html convert the empty equations "${}$" to pictures and we can see empty rectangles
    Hans> on the browser. Later on, one of the TeX gurus, Don Arseneau, pointed me to rcs.sty. I
    Hans> tried it and it worked well.  However, rcs.sty is not part of the tetex instalation
    Hans> package.  How should we go about using this package? Should we put it under htdocs/tex
    Hans> subdir or should we let the users install their own rcs.sty?
you can put it in htdocs/tex
this is the place for tex/latex2html related files

    Hans> Another question: there are two date strings on the title. "May 8, 2000" and
    Hans> "Documentation revised May 14, 2000". What are these dates? Which one can be generated by
    Hans> RCS keyword $Date$?
the first date is the date of creation 
the second dsate is the revision date
the second must be changed

    Hans> Once the issues are finalized I'll make another cvs commit.
good 


where are we on the packages side Frank ? did you have the time to check the packages 
I put on corelinux.sourforge.net ?
what is the schedule for the next release?

regards
christophe

Re: [Corelinux-develop] PDF generation problem fixed.

[Frank V. C. <fr...@co...>]

Hans - Dulimarta wrote:
> 
> On Thu, 13 Jul 2000, Frank V. Castellucci wrote:
> 
> > Date: Thu, 13 Jul 2000 07:31:16 -0400
> > From: Frank V. Castellucci <fr...@co...>
> > To: Hans - Dulimarta <dul...@eg...>
> > Subject: Re: Commited?
> >
> > Hans - Dulimarta wrote:
> > >
> >
> > I see you fixed the problem, although I am having access problems to CVS
> > at this time I will get it later and test it.
> >
> 
> I also fixed the error which occured when generating the PDF output.
> Apparently, pdflatex complained about 'old toc file exist'. So, I modified
> the Makefile to remove $(CORE).toc before running pdflatex.

Cool

> 
> > Another thing to note, when the PDF, DVI, etc. are built they are also
> > checked in because at the moment we can't build them on the shell server
> > (for web access) because the tools aren't there. I know this is
> > inconvenient and we should discuss changes for the future. Maybe the
> > compile farm server would be ideal.
> 
> I'll check them in as well.

I'll keep an eye out and then as long as Christophe doesn't complain
I'll get the 0.4.25 together (Docs + tar.gz) and let him have at
creating the packages. I then upload (ftp) to sourceforge and viola!
 
> >
> > With packages about to be released, it is a great time to discuss who
> > wants to do what. There are really no limitations (Docs, Code, Web,
> > Frameworks, Utilities, Applications) at this time, and although there
> > are plenty of required types and function still missing from core, it
> > doesn't preclude some framework expansion.
> >
> 
> If you look at the cppstnd.tex document, you'll find something like
> "${}$Revision: 1.3 ${}$". This is a TeX trick which I learned from the
> comp.text.tex newsgroup to incorporate RCS keyword in LaTeX documents.
> The trick works for the .dvi, .ps. and .pdf output, but not for the .html
> output.
> 
> latex2html convert the empty equations "${}$" to pictures and we can
> see empty rectangles on the browser. Later on, one of the TeX gurus, Don
> Arseneau, pointed me to rcs.sty. I tried it and it worked well.
> However, rcs.sty is not part of the tetex instalation package.
> How should we go about using this package? Should we put it under
> htdocs/tex subdir or should we let the users install their own rcs.sty?

If re-distributing rcs.sty doesn't cause a license snafu in regards to
the CoreLinux LGPL, I have no problem with including it in htdocs/tex.
This is primarily for tarball or CVS grabs of the system, the doc
package I do just pulls the resulting *.dvi, *.pdf, etc.
 
> Another question: there are two date strings on the title. "May 8, 2000"
> and "Documentation revised May 14, 2000". What are these dates? Which one
> can be generated by RCS keyword $Date$?
> 
> Once the issues are finalized I'll make another cvs commit.

There should be one date, the "Documentation revised" one with the RCS
$Date$. The other is a throw back to the StarOffice HTML editor macros,
long gone away now.

Thanks Hans!

Frank

[Corelinux-develop] PDF generation problem fixed.

[Hans - D. <dul...@eg...>]

On Thu, 13 Jul 2000, Frank V. Castellucci wrote:

> Date: Thu, 13 Jul 2000 07:31:16 -0400
> From: Frank V. Castellucci <fr...@co...>
> To: Hans - Dulimarta <dul...@eg...>
> Subject: Re: Commited?
> 
> Hans - Dulimarta wrote:
> > 
> 
> I see you fixed the problem, although I am having access problems to CVS
> at this time I will get it later and test it.
>

I also fixed the error which occured when generating the PDF output.
Apparently, pdflatex complained about 'old toc file exist'. So, I modified
the Makefile to remove $(CORE).toc before running pdflatex.
 
> Another thing to note, when the PDF, DVI, etc. are built they are also
> checked in because at the moment we can't build them on the shell server
> (for web access) because the tools aren't there. I know this is
> inconvenient and we should discuss changes for the future. Maybe the
> compile farm server would be ideal.

I'll check them in as well.

> 
> In addition, you should "subscribe" to the corelinux-develop mailing
> list. Otherwise I have to go and approve every post from outside.

I just did.

> 
> With packages about to be released, it is a great time to discuss who
> wants to do what. There are really no limitations (Docs, Code, Web,
> Frameworks, Utilities, Applications) at this time, and although there
> are plenty of required types and function still missing from core, it
> doesn't preclude some framework expansion.
>

If you look at the cppstnd.tex document, you'll find something like
"${}$Revision: 1.3 ${}$". This is a TeX trick which I learned from the
comp.text.tex newsgroup to incorporate RCS keyword in LaTeX documents.  
The trick works for the .dvi, .ps. and .pdf output, but not for the .html
output.

latex2html convert the empty equations "${}$" to pictures and we can
see empty rectangles on the browser. Later on, one of the TeX gurus, Don
Arseneau, pointed me to rcs.sty. I tried it and it worked well.
However, rcs.sty is not part of the tetex instalation package.
How should we go about using this package? Should we put it under
htdocs/tex subdir or should we let the users install their own rcs.sty?

Another question: there are two date strings on the title. "May 8, 2000"
and "Documentation revised May 14, 2000". What are these dates? Which one
can be generated by RCS keyword $Date$?

Once the issues are finalized I'll make another cvs commit.

> I am just happy you guys have contributed at all.
> 
> See you on the corelinux-develop list!
> 
> 

-- 
Hans Dulimarta, Ph.D.             dulimart@[egr.msu.edu, computer.org]
Visiting Research Associate         http://www.egr.msu.edu/%7edulimart   
                           Ph: (517)432-7589  Fax2Email: (760)281-7691
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

[Corelinux-develop] Ignore test

[Frank V. C. <fr...@co...>]

Try again to avoid admin notification and approval

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

[Corelinux-develop] Ping

[Frank V. C. <fr...@co...>]

Testing round trip on new list.

-- 
Frank V. Castellucci

[Corelinux-develop] Re: [Bug #109336] Inconsistent examples in C++ coding standard

[Hans - D. <dul...@eg...>]

On Wed, 12 Jul 2000 no...@so... wrote:

> Date: Wed, 12 Jul 2000 05:11:26 -0700
> From: no...@so...
> To: dul...@eg..., dul...@eg...
> Subject: [Bug #109336] Inconsistent examples in C++ coding standard 
> 
> Bug #109336, was updated on 2000-Jul-12 01:30
> Here is a current snapshot of the bug.
> 
> Project: CoreLinux++
> Category: Documentation
> Status: Open
> Resolution: None
> Bug Group: Defects
> Priority: 5
> Summary: Inconsistent examples in C++ coding standard 
> 
> Details: Some examples code given in the Standards & Guidelines
> are inconsistent with the standards/guidelines.
> 
> Follow-Ups:
> 
> Date: 2000-Jul-12 08:11
> By: frankc
> 
> Comment: I have re-opened this because on my machine it stops and
> prompts me with a question mark and a error reporting:
> 
> ! Argument of \@fifhoffive has an extra }.
> <inserted text>
> 	\par
> 1.1913 ...g the Section~\wref{sec:Class-Functions}
> ?
> 

This is the same error message that I got when generating the PDF output
mentioned in my Jul 10 e-mail. I tried both \ref and \vref and got the
same message. [Perhaps, I mistyped the \vref as \wref when switching back
from \ref to \vref].

I "fixed" it by commenting the inclusion of the hyperref package.

Since you said it worked OK on your machine, I uncommented the lines
and did cvs commit. I'll fix it later today. 

> At which point I hit enter. As this needs to run automatically
> unattended there may be no-one there to hear the tree fall in the
> forest! ;-> 
> -------------------------------------------------------
> 
> For detailed info, follow this link:
> http://sourceforge.net/bugs/?func=detailbug&bug_id=109336&group_id=308
> 

-- 
Hans Dulimarta, Ph.D.             dulimart@[egr.msu.edu, computer.org]
Visiting Research Associate         http://www.egr.msu.edu/%7edulimart   
                           Ph: (517)432-7589  Fax2Email: (760)281-7691
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

[Corelinux-develop] Test

[Frank V. C. <fr...@co...>]

Just testing
-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package