On 3 May 2015 at 20:55, Gareth France <gareth.fra...@cliftonts.co.uk> wrote:
> My brain still hurts from figuring out everything I have done so far. I'd
> rather not have to start again if I can at all help it. As you say there
> will be a correct way to do this and I would hope that being pointed to that
> correct way I would be able to do so with the tools I am already using. I
> shall keep this message highlighted but I'd like to hold off looking at this
> sword thing for as long as possible, it sounds like it might just be the
> straw that broke the camel's back!

I thought you had got over the problem that Barry is addressing.  That
was the debian/source/format:3.0 (quilt) was it not?

No-one has replied to my suggestion that the answer to the path
problem is to install the s/w in /opt and put a link to the program in
/usr/bin/.  That is the way that teamviewer does it, for example

$ ls /opt/teamviewer9/
config  doc  logfiles  tv_bin

$ ls -l /usr/bin/teamviewer
lrwxrwxrwx 1 root root 41 Sep  4  2014 /usr/bin/teamviewer ->
/opt/teamviewer9/tv_bin/script/teamviewer

The question is whether that satisfies the rules or not.

Colin


>
>
> On 03/05/15 20:52, Barry Drake wrote:
>>
>> On 03/05/15 20:04, Gareth France wrote:
>>>
>>> As most people are now well aware I'm desperate to be able to work out
>>> GUI programming, but it does not seem to be my fate. There must be a
>>> correct way to submit a commercial command line only program. It is
>>> virtually useless if each user must be taught to use the full path each
>>> time.
>>
>>
>> Gareth - I'm away from my main computer at the moment and don't have all
>> the stuff with me.  This is the critical patch from the Sword library
>> package.  I is a copy of Dmitri's original from an earlier Sword Debian
>> package.  I do remember not being able to get it to work properly until
>> I was told to use the chroot version of Debian.  I spent many frustrated
>> hours trying.  There is no gui in the Sword engine - it's pure library
>> binary stuff with the odd commanline program - and it was just fine.
>> Your program does not need to be gui - it just needs to put stuff where
>> Debian/Ubuntu allows it.  pbuilder under debootstrap is very strict, and
>> gives a lot more error messages.
>>
>>
>>
>
> --
> ubuntu-uk@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
> https://wiki.ubuntu.com/UKTeam/

-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

Reply via email to