Re: Problem using "dpkg -i"

[Richard Owlett <rowlett@cloud85.net>]

On 01/16/2018 03:51 PM, Michael Lange wrote:
> On Tue, 16 Jan 2018 15:29:57 -0600
> Richard Owlett <rowlett@cloud85.net> wrote:
>
> > On 01/16/2018 04:17 AM, Michael Lange wrote:
> > > [snip]
> > >
> > > To the OP:
> > > a quick web search showed another alternative that (iirc) has not been
> > > mentioned before, see http://bluegriffon.org/ . I don't know anything
> > > about this program, except that it appears to be commercial but open
> > > source and they have a deb package available (which may or may not
> > > work with debian) and it apparently can be used for free with a
> > > somewhat reduced feature set.
> >
> > That looks interesting. The only problem is I'm still using i386 flavor.
>
> Maybe you could try to build from source? The instructions at
> https://github.com/therealglazou/bluegriffon
> at a quick glance look quite detailed, and I assume you are not
> interested in the expensive extra-features from the binary packages
> anyway?

Thank you.
The original problem which originally prompted me to investigate
"dpkg -i" has been resolved.

*HOWEVER* your post leads to solving a more important problem.
It has been suggested several times "to build from source". I couldn't
find instructions suitable to my lack of background. The closest I've 
come was working in 8080 assembler ~40 years ago ;} Your reference and 
the educational material at https://www.mercurial-scm.org/ should 
resolve that problem.

> Or, the (maybe) easier way, try to pick one of the older releases from
> http://bluegriffon.org/freshmeat/ and see if one of these can be installed
> and run on your system (2.3.1 appears to be the latest that comes with a
> 386 deb).
>
> Regards
>
> Michael