viewmail-info
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [VM] Announcement: 8.2.0a (alpha testing) release


From: Uday S Reddy
Subject: Re: [VM] Announcement: 8.2.0a (alpha testing) release
Date: Wed, 18 May 2011 23:14:59 +0100

address@hidden writes:

>  > Note that you don't need to do `make install' to use VM.  The INSTALL file
>  > gives you instructions on how to use it directly from the directory where
>  > you build VM.
> 
> True but I took your note seriously;

Fair enough.  The reason I suggested using VM from the built directory is
that it appeared as if you needed to go back to the old version of VM just
because `make install' didn't work.  There is obviously more to this release
than the install scripts.  By using alternative methods, you can actually
begin to test the VM proper.

> But then VM itself was unusable.

Right.  It would be useful to get to the bottom of the problem.  If you can
try to be more specific about the errors you have found, we could begin to
investigate it.  What exactly was the error message?  What was the value of
vm-mime-qp-decoder-program?  What happens if you set the variable to the
full path name of the program?

> After a small
> amount of time trying to locate the problem I simply moved all the relevant
> programs to /usr/local/bin, 

This seems to suggest that it wasn't installed in /usr/local/bin to start
with.  So, where did it get installed?

> Note that this report was just noting that the installation process which has
> worked for many years in the past no longer works, and to offer a few details.
> I've not the time to see if any of the suggestions work (especially as they
> don't have anything to do with what appears to be my bad configuration of the
> new VM) but if they do it would be good to add them to the INSTALL file.

Well, the exact words used by Rob F to describe `make install' in the
INSTALL file were:

      Which might work, but might not work as most distros have their own
      directory layout.

So, it is not exactly a cut-and-dried issue.  Some amount of fiddling and
experimentation would be warranted.  Or, you can finesse the issue by just
specifying the full path names for the helper programs in your .vm file.

Cheers,
Uday



reply via email to

[Prev in Thread] Current Thread [Next in Thread]