Re: Request to package: cvsup
On Thu, Apr 15, 1999 at 08:15:45PM +0200, Sven Rudolph wrote:
> Martin Schulze <joey@finlandia.Infodrom.North.DE> writes:
>
> > I wonder why there is no cvsup package yet. Oh well, I guess
> > I know why: It needs a modula-3 compiler which is not available
> > or something.
>
> During the last years several people tried to package the DEC SRC
> Modula-3 compiled. All failed, including me.
>
> It frequently intermixes compiling and installing parts into the final
> location; hence it is quite impossible to package it according to
> Debian standards. Things might have changed lately. And there might be
> other Modula-3 compilers.
Well, I got curious about this cvsup program, looked at the website, read
some about it. It's impressive. And it would be _really_ useful. Reading
the install docs, PM3[1] might be a better bet than DEC SRC. Looked at
that, but it's a 26 MB download -- that's a no-can-do at the moment for me.
Reading PM3's installation guide, the initial package _will_ be a PITA:
| Bootstrap Source Installation
|
| The bootstrap for a platform contains the assembly source for all the
^^^^^^^^^^^^^^^
| files comprising m3build and m3ship, and suitable makefiles. The PATH and
| LD_LIBRARY_PATH environment variables need to be set properly as in the
| previous sections. You may then customize the top level bootstrap makefile
| Makefile if needed, customize the compiler configuration files in
| m3config/src, select the packages to compile in src/m3makefile, and then
| proceed with the compilation and installation (make). The WWW download
| menu allows one to download the bootstrap and source as a single file.
followed by:
| Source only Installation
|
| For a source only distribution, you need a compatible version of m3build
| and m3ship already installed. The PATH and LD_LIBRARY_PATH environment
| variables also need to be set properly as explained in the previous
| section. You may then customize the compiler configuration files in
| m3config/src, select the packages to compile in src/PACKAGES, and then
| proceed with the compilation and installation (m3build). Typically the
| source is downloaded through the WWW download menu, and the ftp transfer
| may be omitted from the following procedure.
After getting the initial compiler right, this should not be more complex
than other compiler's pacakges. The real challenge will be compiling this
for architechtures other than i386...
Anyone here wants to give it a try?
Marcelo
[1] http://m3.polymtl.ca/m3/
Reply to: