Re: :action depend for D

Lars Ivar Igesund wrote:

> From: "Bram Moolenaar" <[email protected]>
> > But if you have a good place to host the files yourself, the package
> > recipe on the A-A-P site can redirect to that.
> 
> I have a good and stable place. It will be natural to have it there
> for others anyway. It is now situated at
> http://www.igesund.net/larsivar/ddepcheck.d

Good.  I'll adjust the package recipe to download that file.

> > A few remarks:
> >
> > I typed the name wrong a few times.  The name "depchkd" could be
> > "depcheckd".  Or perhaps "ddepcheck"?  It's not that important, but once
> > it's chosen it's difficult to change without causing trouble.
> 
> As you see, I've changed it to ddepcheck

OK, I'll change the d module.  Note that I'm currently releasing
versions in CVS only, until we worked out the details.

> > The bootstrap recipe for the package downloads the source, compiles it
> > and moves it to the Aap bin directory.  It looks like you didn't test
> > this: There is no "Global.aap_srcdir".  You can download the file into
> > the current directory and build it there.
> 
> No I didn't test it :)
> 
> > Compiling depchekd.d is done by directly invoking "dmd".  This bypasses
> > the carefully tuned "d" module and "dmd" tool.
> 
> Yes I'm aware. As long as dmd is the only compiler, it's not really a
> problem.  It has to be installed anyway (maybe using ":assertpkg
> {optional}" first).

There is also a problem for people that don't have an internet
connection.  They would not get past this :assertpkg.  Adding {optional}
is possible, but then dependency checking doesn't work...  Is giving a
warning sufficient?  Otherwise, the file could be included in the
distribution somehow.

> > I guess your method to invoke "dmd" directly wasn't such a bad idea.
> 
> It wasn't ;)
> 
> > How about this then:
> 
> >         :sys $dc depchkd.d
> I think we will optimize:
>            :sys $dc -O ddepcheck.d

OK, I'll add the "-O".

> > I have uploaded this, thus you can try it out with "aap --install
> > depchkd".
> 
> Ok, the fetching and installing works as a charm. The problem though
> with it being installed in bindir, is that :sys don't find at since that dir
> isn't in PATH. :assertpkg do, though. Some possible solutions.
> 
> 1. Have the boot.aap install it somewhere that we *knows* is in PATH.
>    (I don't like this solution).
> 
> 2. Instruct the user to add bindir to PATH.
>    (Not automatic enough?)
> 
> 3. Add bindir to PATH automatically at some time.
>    (Shell (atleast cmd.exe) must be restarted before it works)
> 
> 4. Let :sys check bindir too.
>     (A possibly ugly solution?)
> 
> 5. Let the user provide a directory during install.
>     (It is then up to the user to make sure the dir is in PATH)

The Aap way of doing this is to use:

	:progsearch DDEPCHECK ddepcheck

And then use ":sys $DDEPCHECK ..."

I tried using $m_d.DDEPCHECK but that apparently doesn't work...

-- 
ARTHUR:  No, hang on!  Just answer the five questions ...
GALAHAD: Three questions ...
ARTHUR:  Three questions ...  And we shall watch ... and pray.
                 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/