cygport ... install starts in cwd but ... all does not

cygport ... install starts in cwd but ... all does not

[Brian Inglis]

When rerunning a cygport build with "cygport *.cygport all" after fixing up
problems stage by stage, "doicon $NAME.png" at the start of src_install, before
"cd/pushd ${B}" fails with fatal message "*** ERROR: file $NAME.png does not
exist", whereas rerunning "cygport *.cygport install" succeeds without any
messages.

Even changing cd to pushd, and adding popd at the end of each src_... function,
does not solve the issue.

The package does not include an icon, so I downloaded something suitable to the
same package directory as the $NAME.cygport and *.patch PATCH_URI files.

Any alternative approaches that anyone can suggest might work?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]

Re: cygport ... install starts in cwd but ... all does not

[Marco Atzeri]

On 17.05.2020 08:45, Brian Inglis wrote:
> When rerunning a cygport build with "cygport *.cygport all" after fixing up
> problems stage by stage, "doicon $NAME.png" at the start of src_install, before
> "cd/pushd ${B}" fails with fatal message "*** ERROR: file $NAME.png does not
> exist", whereas rerunning "cygport *.cygport install" succeeds without any
> messages.
> 
> Even changing cd to pushd, and adding popd at the end of each src_... function,
> does not solve the issue.
> 
> The package does not include an icon, so I downloaded something suitable to the
> same package directory as the $NAME.cygport and *.patch PATCH_URI files.
> 
> Any alternative approaches that anyone can suggest might work?
> 

can we see the file ?
May be is a banal issue that you are oversighting

Re: cygport ... install starts in cwd but ... all does not

[Brian Inglis]

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On 2020-05-17 02:13, Marco Atzeri via Cygwin-apps wrote:
> On 17.05.2020 08:45, Brian Inglis wrote:
>> When rerunning a cygport build with "cygport *.cygport all" after fixing up
>> problems stage by stage, "doicon $NAME.png" at the start of src_install, before
>> "cd/pushd ${B}" fails with fatal message "*** ERROR: file $NAME.png does not
>> exist", whereas rerunning "cygport *.cygport install" succeeds without any
>> messages.
>>
>> Even changing cd to pushd, and adding popd at the end of each src_... function,
>> does not solve the issue.
>>
>> The package does not include an icon, so I downloaded something suitable to the
>> same package directory as the $NAME.cygport and *.patch PATCH_URI files.
>>
>> Any alternative approaches that anyone can suggest might work?
>>
> 
> can we see the file ?
> May be is a banal issue that you are oversighting

Doh - of course - attached!

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]


[-- Attachment #2: tek4010.cygport --]
[-- Type: text/plain, Size: 3336 bytes --]

#|/usr/bin/cygport
# tek4010.cygport - tek4010 Cygwin package build control script

NAME=tek4010
VERSION=1.5
RELEASE=1

CATEGORY="X11 Shells"
SUMMARY="Tektronix 4010, 4013, 4014, 4015 and ARDS terminal emulator"
DESCRIPTION="
Full support of Tektronix 4010, 4013, 4014, and 4015 storage tube
terminals, and Computer Displays Inc. Advanced Remote Display Station
for Project MAC.
Coordinate system: 4096x3072 Tek points and 1024x780: full screen
resolution in -full mode; standard resolution of 1024x780 points;
scaled smaller resolution for lower resolution screens.
All Tektronix 4014 modes, including graphical input mode (GIN),
write-through mode, grayscale images (Tektronix 4014 intensity chart),
and the bright drawing spot support.
APL character set and keyboard for Tektronix 4013 and Tektronix 4015.
Direct display of GNU and historical plotlib files.
Telnet, rsh, and serial connections to historical host computers and
simulators."

HOMEPAGE="https://github.com/rricharz/Tek4010"
GIT_URI="https://github.com/rricharz/Tek4010.git"
PATCH_URI="makefile.patch tube.c.patch"

inherit git

# no src subdirectory
SRC_DIR=Tek4010

# use DESTDIR
USE_DESTDIR=1

# Build dependencies
DEPEND="make binutils gcc-core libgtk3-devel"

src_compile() {
    pushd ${B}
    lndirs
    /bin/rm -f $NAME
    cygmake
    popd
}

# test must be on terminal: just list version
src_test()
{
    pushd ${B}
    ./$NAME
    /bin/true
    popd
}

inherit font

src_install() {
    doicon Tek4010.png
    pushd ${B}
    cyginstall
    # version log, manuals dir README png
    dodoc versions.txt *.png manuals/*.*
    # APL font and tests
    insinto /usr/share/$NAME/apl
    doins apl/*
    fontinto Apl385
    dofont apl/Apl385.ttf
    # ARDS emulator files
    insinto /usr/share/$NAME/ardsfiles
    doins ardsfiles/*.*
    # plotlib files
    insinto /usr/share/$NAME/pltfiles
    doins pltfiles/*.* *.plt
    insinto /usr/share/$NAME/pltfiles/gsxbasic
    doins pltfiles/gsxbasic/*.*
    insinto /usr/share/$NAME/pltfiles/ICEMD_pltfiles
    doins pltfiles/ICEMD_pltfiles/*.*
    insinto /usr/share/$NAME/pltfiles/More_pltfiles
    doins pltfiles/More_pltfiles/*.*
    insinto /usr/share/$NAME/pltfiles/PointPlot
    doins pltfiles/PointPlot/*.*
    # test programs
    insinto /usr/share/$NAME/tektests
    doins tektests/*
    # demo scripts
    exeinto /usr/share/$NAME/demos
    doexe demo.sh fdemo.sh gdemo.sh demo.sh ICEMD_demo.sh
    # X desktop
    make_desktop_entry "/usr/bin/tek4010 -noexit" Tek4010 Tek4010 \
			'Graphics;Viewer;2DGraphics;VectorGraphics;System;TerminalEmulator;GTK' \
"Tektronix 4010, 4013, 4014, 4015 Storage Tube and ARDS Graphical Display Terminal Emulator" \
			GenericName=Terminal Terminal=no
    popd
}

# SPDX-License-Identifier: MIT-like
LICENSE="GPL3"
LICENSE_SPDX="SPDX-License-Identifier: GPL3"
LICENSE_URI="LICENCE"

CYGWIN_MAINTAINER="Brian%20Inglis"
CYGWIN_MAINTAINER_EMAIL="Brian.Inglis@SystematicSW.ab.ca"
UPSTREAM_MAINTAINER="Rene Richarz"
UPSTREAM_MAINTAINER_EMAIL="rricharz77@gmail.com"
SUBJECT="Package%20$NAME%20$VERSION"
MAILTO="mailto:$UPSTREAM_MAINTAINER_EMAIL,$UPSTREAM_EMAIL\
?to=$UPSTREAM_MAINTAINER%20%3C$UPSTREAM_MAINTAINER_EMAIL%3E\
&to=$UPSTREAM_MAINTAINER%20%3C$UPSTREAM_EMAIL%3E\
&from=$CYGWIN_MAINTAINER%20%3C$CYGWIN_MAINTAINER_EMAIL%3E\
&subject=$SUBJECT&body=$SUBJECT"

# vim:ft=sh:

Re: cygport ... install starts in cwd but ... all does not

[Marco Atzeri]

On 18.05.2020 17:47, Brian Inglis wrote:
> On 2020-05-17 02:13, Marco Atzeri via Cygwin-apps wrote:
>> On 17.05.2020 08:45, Brian Inglis wrote:
>>> When rerunning a cygport build with "cygport *.cygport all" after fixing up
>>> problems stage by stage, "doicon $NAME.png" at the start of src_install, before
>>> "cd/pushd ${B}" fails with fatal message "*** ERROR: file $NAME.png does not
>>> exist", whereas rerunning "cygport *.cygport install" succeeds without any
>>> messages.
>>>
>>> Even changing cd to pushd, and adding popd at the end of each src_... function,
>>> does not solve the issue.
>>>
>>> The package does not include an icon, so I downloaded something suitable to the
>>> same package directory as the $NAME.cygport and *.patch PATCH_URI files.
>>>
>>> Any alternative approaches that anyone can suggest might work?
>>>
>>
>> can we see the file ?
>> May be is a banal issue that you are oversighting
> 
> Doh - of course - attached!
> 

Hi Brian,
may be also the patches ?

Anyway removing most of the cygport to fake the compilation
and installation and putting just some pwd before and after the
pushd/popd to see what is happening:

$ cygport tek4010.cygport compile
 >>> Compiling tek4010-1.5-1.x86_64
/pub/tmp
/pub/tmp/tek4010-1.5-1.x86_64/build
/pub/tmp


$ cygport tek4010.cygport install
 >>> Installing tek4010-1.5-1.x86_64
/pub/tmp
*** ERROR: file Tek4010.png does not exist

so you need a pushd ${S} before

     doicon Tek4010.png
     pushd ${B}


Regards
Marco

Re: cygport ... install starts in cwd but ... all does not

[Brian Inglis]

On 2020-05-19 11:43, Marco Atzeri via Cygwin-apps wrote:
> On 18.05.2020 17:47, Brian Inglis wrote:
>> On 2020-05-17 02:13, Marco Atzeri via Cygwin-apps wrote:
>>> On 17.05.2020 08:45, Brian Inglis wrote:
>>>> When rerunning a cygport build with "cygport *.cygport all" after fixing up
>>>> problems stage by stage, "doicon $NAME.png" at the start of src_install, before
>>>> "cd/pushd ${B}" fails with fatal message "*** ERROR: file $NAME.png does not
>>>> exist", whereas rerunning "cygport *.cygport install" succeeds without any
>>>> messages.
>>>>
>>>> Even changing cd to pushd, and adding popd at the end of each src_... function,
>>>> does not solve the issue.
>>>>
>>>> The package does not include an icon, so I downloaded something suitable to the
>>>> same package directory as the $NAME.cygport and *.patch PATCH_URI files.
>>>>
>>>> Any alternative approaches that anyone can suggest might work?

>>> can we see the file ?
>>> May be is a banal issue that you are oversighting

>> Doh - of course - attached!

> may be also the patches ?

You mean switching to apply during prep?
You are probably right!
Thanks very much for that insight.
Will have to look into what that runs.

> Anyway removing most of the cygport to fake the compilation
> and installation and putting just some pwd before and after the
> pushd/popd to see what is happening:
> 
> $ cygport tek4010.cygport compile
>>>> Compiling tek4010-1.5-1.x86_64
> /pub/tmp
> /pub/tmp/tek4010-1.5-1.x86_64/build
> /pub/tmp
> 
> 
> $ cygport tek4010.cygport install
>>>> Installing tek4010-1.5-1.x86_64
> /pub/tmp
> *** ERROR: file Tek4010.png does not exist

Thanks also for the suggestion of approach to take using pwd around everything.

> so you need a pushd ${S} before
> 
>     doicon Tek4010.png
>     pushd ${B}

SRC_DIR=Tek4010 as the sources are extracted in that directory instead of src.

The local package files .cygport, .patch, .png are all under my main
~/src/cygwin/tek4010/ directory where I invoke cygport, so it starts there, but
seems unable to get back there.

Should be able to get this done and maybe offer an ITP.

Although this package appears designed to build in user home dir under Raspbian
(and Ubuntu, so also Debian), it does not seem to be packaged anywhere I can find.

I'll see if the author would be interested in a packaging PR to remove home dir
dependencies and support Cygwin packaging and its metas, and maybe I could also
add Debian/Raspbian/Ubuntu metas as they are somewhat similar and standard.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]

Re: cygport ... install starts in cwd but ... all does not

[Marco Atzeri]

On 19.05.2020 20:56, Brian Inglis wrote:
> On 2020-05-19 11:43, Marco Atzeri via Cygwin-apps wrote:
>> On 18.05.2020 17:47, Brian Inglis wrote:
>>> On 2020-05-17 02:13, Marco Atzeri via Cygwin-apps wrote:
>>>> On 17.05.2020 08:45, Brian Inglis wrote:

> 
>> may be also the patches ?
> 
> You mean switching to apply during prep?
> You are probably right!
> Thanks very much for that insight.
> Will have to look into what that runs.

I was just saying I can not test the full process,
so I focused on just the doicon ;-)

>> Anyway removing most of the cygport to fake the compilation
>> and installation and putting just some pwd before and after the
>> pushd/popd to see what is happening:
>>
>> $ cygport tek4010.cygport compile
>>>>> Compiling tek4010-1.5-1.x86_64
>> /pub/tmp
>> /pub/tmp/tek4010-1.5-1.x86_64/build
>> /pub/tmp
>>
>>
>> $ cygport tek4010.cygport install
>>>>> Installing tek4010-1.5-1.x86_64
>> /pub/tmp
>> *** ERROR: file Tek4010.png does not exist
> 
> Thanks also for the suggestion of approach to take using pwd around everything.

I am used to have "cd ${S}" or "cd ${B}" as first step,
so I had no clue if there was a default.
Cygport code is not obvious, so adding "pwd" was the
easy way to debug


>> so you need a pushd ${S} before
>>
>>      doicon Tek4010.png
>>      pushd ${B}
> 
> SRC_DIR=Tek4010 as the sources are extracted in that directory instead of src.
> 
> The local package files .cygport, .patch, .png are all under my main
> ~/src/cygwin/tek4010/ directory where I invoke cygport, so it starts there, but
> seems unable to get back there.

I use a common directory for both x86 and x86_64 platform
and the test installation versions of both.

$ readlink -f /pub
/cygdrive/d/cyg_pub

I assume unusual enough that "pwd" is useful a lot

> Should be able to get this done and maybe offer an ITP.
> 
> Although this package appears designed to build in user home dir under Raspbian
> (and Ubuntu, so also Debian), it does not seem to be packaged anywhere I can find.
> 
> I'll see if the author would be interested in a packaging PR to remove home dir
> dependencies and support Cygwin packaging and its metas, and maybe I could also
> add Debian/Raspbian/Ubuntu metas as they are somewhat similar and standard.
> 

The build system seems very basic and old style.
Probably to be as light as possible as the target is a Raspberry Pi.

Regards
Marco

Re: cygport ... install starts in cwd but ... all does not

[Brian Inglis]

On 2020-05-19 14:16, Marco Atzeri via Cygwin-apps wrote:
> On 19.05.2020 20:56, Brian Inglis wrote:
>> On 2020-05-19 11:43, Marco Atzeri via Cygwin-apps wrote:
>>> On 18.05.2020 17:47, Brian Inglis wrote:
>>>> On 2020-05-17 02:13, Marco Atzeri via Cygwin-apps wrote:
>>>>> On 17.05.2020 08:45, Brian Inglis wrote:
> 
>>
>>> may be also the patches ?
>>
>> You mean switching to apply during prep?
>> You are probably right!
>> Thanks very much for that insight.
>> Will have to look into what that runs.
> 
> I was just saying I can not test the full process,
> so I focused on just the doicon ;-)
> 
>>> Anyway removing most of the cygport to fake the compilation
>>> and installation and putting just some pwd before and after the
>>> pushd/popd to see what is happening:
>>>
>>> $ cygport tek4010.cygport compile
>>>>>> Compiling tek4010-1.5-1.x86_64
>>> /pub/tmp
>>> /pub/tmp/tek4010-1.5-1.x86_64/build
>>> /pub/tmp
>>>
>>>
>>> $ cygport tek4010.cygport install
>>>>>> Installing tek4010-1.5-1.x86_64
>>> /pub/tmp
>>> *** ERROR: file Tek4010.png does not exist
>>
>> Thanks also for the suggestion of approach to take using pwd around everything.
> 
> I am used to have "cd ${S}" or "cd ${B}" as first step,
> so I had no clue if there was a default.
> Cygport code is not obvious, so adding "pwd" was the
> easy way to debug
> 
> 
>>> so you need a pushd ${S} before
>>>
>>>      doicon Tek4010.png
>>>      pushd ${B}
>>
>> SRC_DIR=Tek4010 as the sources are extracted in that directory instead of src.
>>
>> The local package files .cygport, .patch, .png are all under my main
>> ~/src/cygwin/tek4010/ directory where I invoke cygport, so it starts there, but
>> seems unable to get back there.
> 
> I use a common directory for both x86 and x86_64 platform
> and the test installation versions of both.
> 
> $ readlink -f /pub
> /cygdrive/d/cyg_pub
> 
> I assume unusual enough that "pwd" is useful a lot
> 
>> Should be able to get this done and maybe offer an ITP.
>>
>> Although this package appears designed to build in user home dir under Raspbian
>> (and Ubuntu, so also Debian), it does not seem to be packaged anywhere I can
>> find.
>>
>> I'll see if the author would be interested in a packaging PR to remove home dir
>> dependencies and support Cygwin packaging and its metas, and maybe I could also
>> add Debian/Raspbian/Ubuntu metas as they are somewhat similar and standard.

On the project Github issues, someone already built and is using on Cygwin, so I
will ask about packaging and some other requirements that came up there.

> The build system seems very basic and old style.
> Probably to be as light as possible as the target is a Raspberry Pi.

Lack of any (interest in?) packaging background, but not development, and not
that light, as this project just provides an X Window Tek emulator front end,
under Debian LXDE X client and server, possibly over ssh or VNC, for a SimH
PDP-11 (or PDP-8 for PiDP-8 emulated console) simulator running original Unix V7
or BSD 2.11 OS and graphics apps driving the Tek, inside a PiDP-11 providing a
hardware interface to miniature emulated console switches and blinkenlights as
well as a hardware serial port connected into the simulator:

	https://obsolescence.wixsite.com/obsolescence/pidp-11

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]