|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-28 19:32:41
|
Ok I just updated my cvs.
DONE:
-----
o changed debian packages creation
- libcorelinux : shared libs
- libcorelinux-dev : static lib+header files+manual pages
- libcorelinux-doc : reference manual in PS/PDF/HTML
- libcorelinux-examples: examples for corelinux with automated Makefile
creation to compile them
o changed lib name (now -lcl++) and shared lib do not use -release anymore
o added doxygen support see doc/
o updated also the ChangeLog with the correct Features added and
bugs fixed
o added a C symbol(ACCheckCoreLinux) in -lcl++ in corelinux.cpp so that
corelinux users using autoconf can detect corelinux presence using
AC_CHECK_LIB
TODO:
-----
o I have still to finish the redhat .spec file
o document the ACCheckCoreLinux feature in Developper manual
o create a README.packages to document package creation
and packages contents
regards
C.
--
Christophe Prud'homme |
MIT, 77, Mass Ave, Rm 3-243 | To err is human,
Cambridge MA 02139 | to repent, divine,
Tel (Office) : (00 1) (617) 253 0229 | to persist, devilish.
Fax (Office) : (00 1) (617) 258 8559 | -- Benjamin Franklin
http://augustine.mit.edu/~prudhomm |
Following the hacker spirit
|
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-28 20:07:13
|
I just received a notification for the post installation corruption of deb packages bug(see below) saying that it was re-opened I opened it today and I closed it since the -2 packages are here and the -1 are removed does it still have to be open ? Bug #110441, was updated on 2000-Jul-28 11:49 Here is a current snapshot of the bug. Project: CoreLinux++ Category: libcorelinux++ Status: Open Resolution: None Bug Group: Severity 2 - incorrect IO Priority: 5 Summary: debian package version 1, post install corrupted Details: post installation problem in the first version of 0.4.25 debian package For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=110441&group_id=308 |
|
From: Frank V. C. <fr...@co...> - 2000-07-28 20:22:34
|
Whenever the state of a defect/feature changes, you get e-mail notification if you are the handler or person who submitted. But, I think SourceForge let out a big belch and things may have gotten reset. But, do not CLOSE, use Fixed instead so I have something available to remind me of what goes into the ChangeLog when we do across the board releases. Frank Christophe Prud'homme wrote: > I just received a notification for > the post installation corruption of deb packages bug(see below) > saying that it was re-opened > > I opened it today and I closed it since the -2 packages are here > and the -1 are removed > > does it still have to be open ? > > Bug #110441, was updated on 2000-Jul-28 11:49 > Here is a current snapshot of the bug. > > Project: CoreLinux++ > Category: libcorelinux++ > Status: Open > Resolution: None > Bug Group: Severity 2 - incorrect IO > Priority: 5 > Summary: debian package version 1, post install corrupted > > Details: post installation problem in the first version of 0.4.25 debian package > > For detailed info, follow this link: > http://sourceforge.net/bugs/?func=detailbug&bug_id=110441&group_id=308 > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-28 20:34:48
|
>>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:
Frank> Whenever the state of a defect/feature changes, you get e-mail notification if you are
Frank> the handler or person who submitted.
yes I knew that
Frank> But, do not CLOSE, use Fixed instead so I have something available to remind me of what
Frank> goes into the ChangeLog when we do across the board releases.
Ok
I think there is a bug in sourceforge when submitting a bug
if you try to assign it to someone it won't work
you have to submit, edit it and reassign it
C.
--
Christophe Prud'homme | A classic is something that
MIT, 77, Mass Ave, Rm 3-243 | everyone wants to have read and
Cambridge MA 02139 | nobody wants to read.
Tel (Office) : (00 1) (617) 253 0229 | -- Mark Twain,
Fax (Office) : (00 1) (617) 258 8559 | "The Disappearance of Literature"
http://augustine.mit.edu/~prudhomm |
Following the hacker spirit
|
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-29 03:38:34
|
We are getting closer to rpm packaging now we have: o libcorelinux o libcorelinux-dev o libcorelinux-doc TODO: ----- o libcorelinux-examples will be more painful Do you guys know how to not restart a rpm building from scratch? each time it erases everything and restarts, so debugging/implementing the spec file is really painful Fortunately I have a dual pentium III 750 so the -j 2 option of make is really a winner, but that's brutal force is there anything like time-stamp? or being able to restart the process at a certain point? help would be much appreciated :) I can't believe there is nothing like that one more question(I am not very fluent in redhat systems) where each of the packages should go, I mean which categories? regards C. -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | If it doesn't work, force it. Cambridge MA 02139 | If it breaks, it needed Tel (Office) : (00 1) (617) 253 0229 | replacing anyway. Fax (Office) : (00 1) (617) 258 8559 | http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Hans - D. <dul...@eg...> - 2000-07-29 03:47:38
|
On Fri, 28 Jul 2000, Christophe Prud'homme wrote: > Date: Fri, 28 Jul 2000 23:38:31 -0400 (EDT) > From: Christophe Prud'homme <pru...@MI...> > Reply-To: cor...@li... > To: cor...@li... > Subject: [Corelinux-develop] rpm packages > > We are getting closer to rpm packaging > now we have: > o libcorelinux > o libcorelinux-dev > o libcorelinux-doc > > TODO: > ----- > o libcorelinux-examples will be more painful > > > Do you guys know how to not restart a rpm building from scratch? Not me. > each time it erases everything and restarts, so debugging/implementing > the spec file is really painful > Fortunately I have a dual pentium III 750 so the -j 2 option of make is > really a winner, but that's brutal force > > is there anything like time-stamp? or being able to restart the process > at a certain point? > help would be much appreciated :) > I can't believe there is nothing like that > > one more question(I am not very fluent in redhat systems) > where each of the packages should go, I mean which categories? > > regards > C. > > -- Hans Dulimarta, Ph.D. dulimart@[egr.msu.edu, computer.org] Visiting Research Associate http://www.egr.msu.edu/~dulimart Ph: (517)432-7589 Fax2Email: (760)281-7691 Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824 |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-29 04:05:47
|
The rpm packaging is done :) the examples appeared to be easy using the scripts I used for debian I will upload the deb/rpm packages to corelinux.sourceforge.net/packages so that you can give some feedback a corelinux.spec.in file will appear in your cvs to generate the packages you have to do: > autorun.sh > configure --> will generate corelinux.spec [1] > make rpm --> you must have read-write access /usr/src/redhat or be root then take a coffee or a tea and relax, it takes some time ! Footnotes: [1] automatic versioning Frank! You will be happy, this one more to not worry about when releasing corelinux :) |
|
From: Frank V. C. <fr...@co...> - 2000-07-29 06:06:25
|
Christophe Prud'homme wrote: > > The rpm packaging is done :) > > the examples appeared to be easy using the scripts I used for debian > I will upload the deb/rpm packages to corelinux.sourceforge.net/packages > so that you can give some feedback > > a corelinux.spec.in file will appear in your cvs > to generate the packages you have to do: > > > autorun.sh > > configure --> will generate corelinux.spec [1] > > make rpm --> you must have read-write access /usr/src/redhat or be root > > then take a coffee or a tea and relax, it takes some time ! > > Footnotes: > [1] automatic versioning Frank! You will be happy, this one more > to not worry about when releasing corelinux :) :-> Cool stuff, I will download and build as well as install and test. So when the smoke clears, I will be genning the rpm packages, tarball, PDF, DVI, TeX, and you will be doing the deb packages until we can get the compile farm machine to outfit the whole thing yes? -- Frank V. Castellucci |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-29 06:35:30
|
Frank> Cool stuff, I will download and build as well as install and test. So when the smoke
Frank> clears, I will be genning the rpm packages, tarball, PDF, DVI, TeX, and you will be doing
Frank> the deb packages until we can get the compile farm machine to outfit the whole thing yes?
yes!
I forsee one problem:
the reference generated by doxygen
I build the manual during the package creation so if you do not have
doxygen/latex installed that we'll be a problem :(
regards
C.
--
Christophe Prud'homme |
MIT, 77, Mass Ave, Rm 3-243 | He that breaks a thing to find out
Cambridge MA 02139 | what it is has left the path of wisdom.
Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien
Fax (Office) : (00 1) (617) 258 8559 |
http://augustine.mit.edu/~prudhomm |
Following the hacker spirit
|
|
From: Frank V. C. <fr...@co...> - 2000-07-29 11:16:15
|
Christophe Prud'homme wrote: > > Frank> Cool stuff, I will download and build as well as install and test. So when the smoke > Frank> clears, I will be genning the rpm packages, tarball, PDF, DVI, TeX, and you will be doing > Frank> the deb packages until we can get the compile farm machine to outfit the whole thing yes? > yes! > I forsee one problem: > the reference generated by doxygen > I build the manual during the package creation so if you do not have > doxygen/latex installed that we'll be a problem :( > > regards > C. I was having some problem with 'make rpm'. I am running again (I installed doxygen) and will report back if a problem. -- Frank V. Castellucci |
|
From: Frank V. C. <fr...@co...> - 2000-07-29 11:42:10
Attachments:
err.txt.gz
|
Christophe Prud'homme wrote: > > The rpm packaging is done :) > > the examples appeared to be easy using the scripts I used for debian > I will upload the deb/rpm packages to corelinux.sourceforge.net/packages > so that you can give some feedback > > a corelinux.spec.in file will appear in your cvs > to generate the packages you have to do: > > > autorun.sh > > configure --> will generate corelinux.spec [1] > > make rpm --> you must have read-write access /usr/src/redhat or be root > > then take a coffee or a tea and relax, it takes some time ! > > Footnotes: > [1] automatic versioning Frank! You will be happy, this one more > to not worry about when releasing corelinux :) This captures the error at which point the 'make rpm' hangs waiting for, yechh, human intervention. -- Frank V. Castellucci |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-29 19:16:33
|
does it appear when you go in doc/ and type make ref ? I cvs updated corelinux/doc there is a new corelinux.cfg.in which should correct the problem! it seems that we do not have the same latex installation I removed the package html as an extra package! just type make in corelinux/doc to regenerate the corelinux.cfg and go in latex to type make pdf to see if the problem is still there if it is ok then the package creation should be fine C. -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | I respect faith, but doubt is Cambridge MA 02139 | what gives you an education. Tel (Office) : (00 1) (617) 253 0229 | -- Wilson Mizner Fax (Office) : (00 1) (617) 258 8559 | http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Frank V. C. <fr...@co...> - 2000-07-29 19:48:29
|
Christophe Prud'homme wrote: > > does it appear when you go in doc/ > and type make ref ? > > I cvs updated corelinux/doc there is a new corelinux.cfg.in > which should correct the problem! > it seems that we do not have the same latex installation > I removed the package html as an extra package! > > just type make in corelinux/doc to regenerate the corelinux.cfg > and go in latex to type make pdf to see if the problem is still there > if it is ok then the package creation should be fine > > C. Ok, that fixed the rpm builds! I will now be testing install/uninstall and let you know if anything crops up! -- Frank V. Castellucci |