Re: [Xastir] New Xastir build

[Tom Henderson]

I'm the good looking one. :-)

KM4UQB

Tom Henderson

On 02/15/2018 09:45 AM, David A Aitcheson wrote:

You're welcome Tom.

I am curious as to which "Tom Henderson" you are on QRZ.com?

73
Dave
KB3EFS


On 02/15/2018 07:52 AM, Tom Henderson wrote:

Thanks for this. Quite simple, and most importantly, it worked. :-)

Tom Henderson

On 02/14/2018 08:00 PM, David A Aitcheson wrote:

Hi Joe,

The short simple answer is:

Open a terminal window and cd to your xastir directory in your src or
source directory.

Confirm that "update-xastir" is in that directory with a ls -la
update-xastir at the command line prompt

Run that script with the command ./update-xastir

It well do some things and then ask you for your user password so it 
can

do the sudo section of its command list.

It is very well behaved and is how I stay up to date.

73
Dave
KB3EFS



___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir





___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[David A Aitcheson]

You're welcome Tom.

I am curious as to which "Tom Henderson" you are on QRZ.com?

73
Dave
KB3EFS


On 02/15/2018 07:52 AM, Tom Henderson wrote:
> Thanks for this. Quite simple, and most importantly, it worked. :-)
>
> Tom Henderson
>
> On 02/14/2018 08:00 PM, David A Aitcheson wrote:
>> Hi Joe,
>>
>> The short simple answer is:
>>
>> Open a terminal window and cd to your xastir directory in your src or
>> source directory.
>>
>> Confirm that "update-xastir" is in that directory with a ls -la
>> update-xastir at the command line prompt
>>
>> Run that script with the command ./update-xastir
>>
>> It well do some things and then ask you for your user password so it can
>> do the sudo section of its command list.
>>
>> It is very well behaved and is how I stay up to date.
>>
>> 73
>> Dave
>> KB3EFS
>>
>
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[Tom Henderson]

Thanks for this. Quite simple, and most importantly, it worked. :-)

Tom Henderson

On 02/14/2018 08:00 PM, David A Aitcheson wrote:

Hi Joe,

The short simple answer is:

Open a terminal window and cd to your xastir directory in your src or
source directory.

Confirm that "update-xastir" is in that directory with a ls -la
update-xastir at the command line prompt

Run that script with the command ./update-xastir

It well do some things and then ask you for your user password so it can
do the sudo section of its command list.

It is very well behaved and is how I stay up to date.

73
Dave
KB3EFS



___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[ru...@bogodyn.org]

On Wed, Feb 14, 2018 at 09:11:54PM -0500, we recorded a bogon-computron 
collision of the <j...@laferla.ca> flavor, containing:
> Sorry Tom, I can see your confusion.  What I did last time was to run Lee???s 
> script for Raspberry pi.   After that, all I did some time ago was to run 
> ./update-xastir in ~./src/Xastir.  Looking at the update-xastir script, it 
> seems that???s what I should do.  Is that correct?  And if I run 
> update-xastir periodically, I should be keeping it up to date, without the 
> need to do separate compile/make.

All "update-xastir" does is
   git pull
   ./bootstrap.sh
   mkdir build
   cd build
   ../configure
   make
   sudo make install

with a few flourishes like saving the results of the entire process to a log
file.  It does a few unnecessary things like chmods on the installed file,
which should be already taken care of unless you've got a strange umask set.

So *it's* doing the "separate compile/make" for you.  I suppose there's a 
convenience to the script, but personally I prefer to do the steps myself.

> Sent from Mail for Windows 10
> 
> From: Tom Russo
> Sent: Wednesday, February 14, 2018 6:15 PM
> To: Xastir - APRS client software discussion
> Subject: Re: [Xastir] New Xastir build
> 
> On Wed, Feb 14, 2018 at 05:50:02PM -0500, we recorded a bogon-computron 
> collision of the <j...@laferla.ca> flavor, containing:
> > I was just wondering whether I should install the new Xastir alongside the 
> > current version (in new directories of course) or simply run the Lee???s 
> > script in the current directories.  I have never had to do this before, so 
> > would appreciate some help.  Or should I uninstall the current version, 
> > which is installed from source.
> 
> When you say you have already installed Xastir from source, was it source from
> Git, or the old 2.0.8 tarball from Sourceforge?
> 
> There is NO difference between the 2.1.0 tarball code and the git master
> branch except a version number.  If you're already building from git master, 
> don't bother installing 2.1.0.  You can just "git pull" in your source clone 
> directory again and rebuild/reinstall in the same build directory you used 
> last time.  That's what using the live git version is all about --- you don't 
> bother to wait for releases (which these days come very rarely, although I 
> hope to fix that), and you get the incremental fixes as they happen.
> 
> If you're using 2.0.8 tarballs, just pull down the 2.1.0 tarball from
> Github and do what you did to build  and install 2.0.8 --- it'll overwrite 
> the 
> old one.
> 
> I can't really see any reason to install the new one in a separate place, or
> to remove the old one first.  The only reason I can see to uninstall the old
> version is if it's really old (like 2.0.6 or 2.0.4) and you want to get rid
> of the old, broken .geos for servers that went away and which those old 
> versions installed.  
> 
> The only reason I can see to uninstall Xastir before upgrading is if the
> old install is from a package management system --- in that case, the new
> source-built would be installing to /usr/local, and the old was installed in
> /usr.  And then there are issues with fixing up your xastir.cnf and other 
> config files.  But that's not what you said you did, so that's not an issue.
> 
> I don't even see much benefit to re-running helper scripts to do the new 
> build,
> either.  Most of those are great ways to get the first build done, because 
> they
> take care of installing all the dependent libraries for you.  But if you've
> already got a build, you've already got those libraries, and the rest of it 
> is 
> just "configure" and "make" and "sudo make install." 
> 
> -- 
> Tom RussoKM5VY
> Tijeras, NM  
> 
>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]
> 
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
> 

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[Tom Russo]

On Wed, Feb 14, 2018 at 09:43:57PM -0500, we recorded a bogon-computron 
collision of the <lee.bengs...@gmail.com> flavor, containing:
> On Feb 14, 2018 9:12 PM, "Joseph LaFerla" <j...@laferla.ca> wrote:
> 
> Sorry Tom, I can see your confusion.  What I did last time was to run Lee???s
> script for Raspberry pi.   After that, all I did some time ago was to run
> ./update-xastir in ~./src/Xastir.  Looking at the update-xastir script, it
> seems that???s what I should do.  Is that correct?  And if I run
> update-xastir periodically, I should be keeping it up to date, without the
> need to do separate compile/make.
> 
> Joe
> 
> 
> The update-xastir script should work.  I prefer to do it more cleanly by
> renaming
> ~./src/Xastir to something like ~./src/Xastir2, and then doing the
> following wiki steps.
>
> >From inside ~/src, issue ...
> 
> git clone https://github.com/Xastir/Xastir.git

Well, this certainly will work, but forces you to download the entire
repository, complete with the entire history of the project since 2003.

If you do a "git pull" in the directory you got from the first clone, it 
downloads *only* what changed since the last time you did it.  Try it, you'll 
like it.

>   cd Xastir
>./bootstrap.sh
> 
>cd ~/src/Xastir
> mkdir build
> cd build
> ../configure CPPFLAGS="-I/usr/include/geotiff"
> 
>make
>sudo make install
> 
> Just a personal preference of working with a brand new source download of
> the latest and greatest. You could also get the same result by doing the
> same directory renaming and running my script.  As Tom pointed out, the
> script would try to reinstall the dependent packages, so it's kind of
> overkill.
> 
> Lee - K5DAT
> 
> 
> From: Tom Russo
> Sent: Wednesday, February 14, 2018 6:15 PM
> To: Xastir - APRS client software discussion
> Subject: Re: [Xastir] New Xastir build
> 
> On Wed, Feb 14, 2018 at 05:50:02PM -0500, we recorded a bogon-computron
> collision of the <j...@laferla.ca> flavor, containing:
> > I was just wondering whether I should install the new Xastir alongside
> the current version (in new directories of course) or simply run the
> Lee???s script in the current directories.  I have never had to do this
> before, so would appreciate some help.  Or should I uninstall the current
> version, which is installed from source.
> 
> When you say you have already installed Xastir from source, was it source
> from
> Git, or the old 2.0.8 tarball from Sourceforge?
> 
> There is NO difference between the 2.1.0 tarball code and the git master
> branch except a version number.  If you're already building from git master,
> don't bother installing 2.1.0.  You can just "git pull" in your source clone
> directory again and rebuild/reinstall in the same build directory you used
> last time.  That's what using the live git version is all about --- you
> don't
> bother to wait for releases (which these days come very rarely, although I
> hope to fix that), and you get the incremental fixes as they happen.
> 
> If you're using 2.0.8 tarballs, just pull down the 2.1.0 tarball from
> Github and do what you did to build  and install 2.0.8 --- it'll overwrite
> the
> old one.
> 
> I can't really see any reason to install the new one in a separate place, or
> to remove the old one first.  The only reason I can see to uninstall the old
> version is if it's really old (like 2.0.6 or 2.0.4) and you want to get rid
> of the old, broken .geos for servers that went away and which those old
> versions installed.
> 
> The only reason I can see to uninstall Xastir before upgrading is if the
> old install is from a package management system --- in that case, the new
> source-built would be installing to /usr/local, and the old was installed in
> /usr.  And then there are issues with fixing up your xastir.cnf and other
> config files.  But that's not what you said you did, so that's not an issue.
> 
> I don't even see much benefit to re-running helper scripts to do the new
> build,
> either.  Most of those are great ways to get the first build done, because
> they
> take care of installing all the dependent libraries for you.  But if you've
> already got a build, you've already got those libraries, and the rest of it
> is
> just "configure" and "make" and "sudo make install."
> 
> --
> Tom RussoKM5VY
> Tijeras, NM
> 
>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[Joseph LaFerla]

Yes Lee I understand your logic.  However I have since run the update-xastir 
script and it seemed to work.  Took a long time and at various points showed 
warnings of variables that are set and not used but it continued running.  I am 
trying to find where I could use the feature of support for wxnow.txt weather 
stations.  I looked in interface control and could not find it.  Also, I am 
interested in the support for proportional fonts in map labels.

I wonder if someone would point me in the right direction please or to the wiki 
where I can check it out myself.

Thanks.

Joe


Sent from Mail for Windows 10

From: Lee Bengston
Sent: Wednesday, February 14, 2018 9:44 PM
To: Xastir - APRS client software discussion
Subject: Re: [Xastir] New Xastir build

On Feb 14, 2018 9:12 PM, "Joseph LaFerla" <j...@laferla.ca> wrote:

Sorry Tom, I can see your confusion.  What I did last time was to run Lee’s
script for Raspberry pi.   After that, all I did some time ago was to run
./update-xastir in ~./src/Xastir.  Looking at the update-xastir script, it
seems that’s what I should do.  Is that correct?  And if I run
update-xastir periodically, I should be keeping it up to date, without the
need to do separate compile/make.

Joe


The update-xastir script should work.  I prefer to do it more cleanly by
renaming
~./src/Xastir to something like ~./src/Xastir2, and then doing the
following wiki steps.

From inside ~/src, issue ...

git clone https://github.com/Xastir/Xastir.git

  cd Xastir
   ./bootstrap.sh

   cd ~/src/Xastir
mkdir build
cd build
../configure CPPFLAGS="-I/usr/include/geotiff"

   make
   sudo make install

Just a personal preference of working with a brand new source download of
the latest and greatest. You could also get the same result by doing the
same directory renaming and running my script.  As Tom pointed out, the
script would try to reinstall the dependent packages, so it's kind of
overkill.

Lee - K5DAT


From: Tom Russo
Sent: Wednesday, February 14, 2018 6:15 PM
To: Xastir - APRS client software discussion
Subject: Re: [Xastir] New Xastir build

On Wed, Feb 14, 2018 at 05:50:02PM -0500, we recorded a bogon-computron
collision of the <j...@laferla.ca> flavor, containing:
> I was just wondering whether I should install the new Xastir alongside
the current version (in new directories of course) or simply run the
Lee???s script in the current directories.  I have never had to do this
before, so would appreciate some help.  Or should I uninstall the current
version, which is installed from source.

When you say you have already installed Xastir from source, was it source
from
Git, or the old 2.0.8 tarball from Sourceforge?

There is NO difference between the 2.1.0 tarball code and the git master
branch except a version number.  If you're already building from git master,
don't bother installing 2.1.0.  You can just "git pull" in your source clone
directory again and rebuild/reinstall in the same build directory you used
last time.  That's what using the live git version is all about --- you
don't
bother to wait for releases (which these days come very rarely, although I
hope to fix that), and you get the incremental fixes as they happen.

If you're using 2.0.8 tarballs, just pull down the 2.1.0 tarball from
Github and do what you did to build  and install 2.0.8 --- it'll overwrite
the
old one.

I can't really see any reason to install the new one in a separate place, or
to remove the old one first.  The only reason I can see to uninstall the old
version is if it's really old (like 2.0.6 or 2.0.4) and you want to get rid
of the old, broken .geos for servers that went away and which those old
versions installed.

The only reason I can see to uninstall Xastir before upgrading is if the
old install is from a package management system --- in that case, the new
source-built would be installing to /usr/local, and the old was installed in
/usr.  And then there are issues with fixing up your xastir.cnf and other
config files.  But that's not what you said you did, so that's not an issue.

I don't even see much benefit to re-running helper scripts to do the new
build,
either.  Most of those are great ways to get the first build done, because
they
take care of installing all the dependent libraries for you.  But if you've
already got a build, you've already got those libraries, and the rest of it
is
just "configure" and "make" and "sudo make install."

--
Tom RussoKM5VY
Tijeras, NM

echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
[n-z][a-m]
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[Lee Bengston]

On Feb 14, 2018 9:12 PM, "Joseph LaFerla" <j...@laferla.ca> wrote:

Sorry Tom, I can see your confusion.  What I did last time was to run Lee’s
script for Raspberry pi.   After that, all I did some time ago was to run
./update-xastir in ~./src/Xastir.  Looking at the update-xastir script, it
seems that’s what I should do.  Is that correct?  And if I run
update-xastir periodically, I should be keeping it up to date, without the
need to do separate compile/make.

Joe


The update-xastir script should work.  I prefer to do it more cleanly by
renaming
~./src/Xastir to something like ~./src/Xastir2, and then doing the
following wiki steps.

From inside ~/src, issue ...

git clone https://github.com/Xastir/Xastir.git

  cd Xastir
   ./bootstrap.sh

   cd ~/src/Xastir
mkdir build
cd build
../configure CPPFLAGS="-I/usr/include/geotiff"

   make
   sudo make install

Just a personal preference of working with a brand new source download of
the latest and greatest. You could also get the same result by doing the
same directory renaming and running my script.  As Tom pointed out, the
script would try to reinstall the dependent packages, so it's kind of
overkill.

Lee - K5DAT


From: Tom Russo
Sent: Wednesday, February 14, 2018 6:15 PM
To: Xastir - APRS client software discussion
Subject: Re: [Xastir] New Xastir build

On Wed, Feb 14, 2018 at 05:50:02PM -0500, we recorded a bogon-computron
collision of the <j...@laferla.ca> flavor, containing:
> I was just wondering whether I should install the new Xastir alongside
the current version (in new directories of course) or simply run the
Lee???s script in the current directories.  I have never had to do this
before, so would appreciate some help.  Or should I uninstall the current
version, which is installed from source.

When you say you have already installed Xastir from source, was it source
from
Git, or the old 2.0.8 tarball from Sourceforge?

There is NO difference between the 2.1.0 tarball code and the git master
branch except a version number.  If you're already building from git master,
don't bother installing 2.1.0.  You can just "git pull" in your source clone
directory again and rebuild/reinstall in the same build directory you used
last time.  That's what using the live git version is all about --- you
don't
bother to wait for releases (which these days come very rarely, although I
hope to fix that), and you get the incremental fixes as they happen.

If you're using 2.0.8 tarballs, just pull down the 2.1.0 tarball from
Github and do what you did to build  and install 2.0.8 --- it'll overwrite
the
old one.

I can't really see any reason to install the new one in a separate place, or
to remove the old one first.  The only reason I can see to uninstall the old
version is if it's really old (like 2.0.6 or 2.0.4) and you want to get rid
of the old, broken .geos for servers that went away and which those old
versions installed.

The only reason I can see to uninstall Xastir before upgrading is if the
old install is from a package management system --- in that case, the new
source-built would be installing to /usr/local, and the old was installed in
/usr.  And then there are issues with fixing up your xastir.cnf and other
config files.  But that's not what you said you did, so that's not an issue.

I don't even see much benefit to re-running helper scripts to do the new
build,
either.  Most of those are great ways to get the first build done, because
they
take care of installing all the dependent libraries for you.  But if you've
already got a build, you've already got those libraries, and the rest of it
is
just "configure" and "make" and "sudo make install."

--
Tom RussoKM5VY
Tijeras, NM

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
[n-z][a-m]
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[Joseph LaFerla]

Sorry Tom, I can see your confusion.  What I did last time was to run Lee’s 
script for Raspberry pi.   After that, all I did some time ago was to run 
./update-xastir in ~./src/Xastir.  Looking at the update-xastir script, it 
seems that’s what I should do.  Is that correct?  And if I run update-xastir 
periodically, I should be keeping it up to date, without the need to do 
separate compile/make.

Joe



Sent from Mail for Windows 10

From: Tom Russo
Sent: Wednesday, February 14, 2018 6:15 PM
To: Xastir - APRS client software discussion
Subject: Re: [Xastir] New Xastir build

On Wed, Feb 14, 2018 at 05:50:02PM -0500, we recorded a bogon-computron 
collision of the <j...@laferla.ca> flavor, containing:
> I was just wondering whether I should install the new Xastir alongside the 
> current version (in new directories of course) or simply run the Lee???s 
> script in the current directories.  I have never had to do this before, so 
> would appreciate some help.  Or should I uninstall the current version, which 
> is installed from source.

When you say you have already installed Xastir from source, was it source from
Git, or the old 2.0.8 tarball from Sourceforge?

There is NO difference between the 2.1.0 tarball code and the git master
branch except a version number.  If you're already building from git master, 
don't bother installing 2.1.0.  You can just "git pull" in your source clone 
directory again and rebuild/reinstall in the same build directory you used 
last time.  That's what using the live git version is all about --- you don't 
bother to wait for releases (which these days come very rarely, although I 
hope to fix that), and you get the incremental fixes as they happen.

If you're using 2.0.8 tarballs, just pull down the 2.1.0 tarball from
Github and do what you did to build  and install 2.0.8 --- it'll overwrite the 
old one.

I can't really see any reason to install the new one in a separate place, or
to remove the old one first.  The only reason I can see to uninstall the old
version is if it's really old (like 2.0.6 or 2.0.4) and you want to get rid
of the old, broken .geos for servers that went away and which those old 
versions installed.  

The only reason I can see to uninstall Xastir before upgrading is if the
old install is from a package management system --- in that case, the new
source-built would be installing to /usr/local, and the old was installed in
/usr.  And then there are issues with fixing up your xastir.cnf and other 
config files.  But that's not what you said you did, so that's not an issue.

I don't even see much benefit to re-running helper scripts to do the new build,
either.  Most of those are great ways to get the first build done, because they
take care of installing all the dependent libraries for you.  But if you've
already got a build, you've already got those libraries, and the rest of it is 
just "configure" and "make" and "sudo make install." 

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[David A Aitcheson]

Hi Joe,

The short simple answer is: 

Open a terminal window and cd to your xastir directory in your src or
source directory.

Confirm that "update-xastir" is in that directory with a ls -la
update-xastir at the command line prompt

Run that script with the command ./update-xastir

It well do some things and then ask you for your user password so it can
do the sudo section of its command list.

It is very well behaved and is how I stay up to date.

73
Dave
KB3EFS

On 02/14/2018 05:50 PM, Joseph LaFerla wrote:
> I was just wondering whether I should install the new Xastir alongside the 
> current version (in new directories of course) or simply run the Lee’s 
> script in the current directories.  I have never had to do this before, so 
> would appreciate some help.  Or should I uninstall the current version, which 
> is installed from source.
>
> Thanks.
>
> Joe
> VA3JLF
>
>
> Sent from Mail for Windows 10
>
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[Tom Russo]

On Wed, Feb 14, 2018 at 05:50:02PM -0500, we recorded a bogon-computron 
collision of the  flavor, containing:
> I was just wondering whether I should install the new Xastir alongside the 
> current version (in new directories of course) or simply run the Lee???s 
> script in the current directories.  I have never had to do this before, so 
> would appreciate some help.  Or should I uninstall the current version, which 
> is installed from source.

When you say you have already installed Xastir from source, was it source from
Git, or the old 2.0.8 tarball from Sourceforge?

There is NO difference between the 2.1.0 tarball code and the git master
branch except a version number.  If you're already building from git master, 
don't bother installing 2.1.0.  You can just "git pull" in your source clone 
directory again and rebuild/reinstall in the same build directory you used 
last time.  That's what using the live git version is all about --- you don't 
bother to wait for releases (which these days come very rarely, although I 
hope to fix that), and you get the incremental fixes as they happen.

If you're using 2.0.8 tarballs, just pull down the 2.1.0 tarball from
Github and do what you did to build  and install 2.0.8 --- it'll overwrite the 
old one.

I can't really see any reason to install the new one in a separate place, or
to remove the old one first.  The only reason I can see to uninstall the old
version is if it's really old (like 2.0.6 or 2.0.4) and you want to get rid
of the old, broken .geos for servers that went away and which those old 
versions installed.  

The only reason I can see to uninstall Xastir before upgrading is if the
old install is from a package management system --- in that case, the new
source-built would be installing to /usr/local, and the old was installed in
/usr.  And then there are issues with fixing up your xastir.cnf and other 
config files.  But that's not what you said you did, so that's not an issue.

I don't even see much benefit to re-running helper scripts to do the new build,
either.  Most of those are great ways to get the first build done, because they
take care of installing all the dependent libraries for you.  But if you've
already got a build, you've already got those libraries, and the rest of it is 
just "configure" and "make" and "sudo make install." 

-- 
Tom RussoKM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] New Xastir build

[Brett Friermood]

Since you have built from source there would be no reason to uninstall, or
worry about installing the new release. If your installation has not been
updated recently, you can run the included script to grab any changes in
source.

Brett KQ9N

On Wed, Feb 14, 2018 at 4:50 PM, Joseph LaFerla  wrote:

> I was just wondering whether I should install the new Xastir alongside the
> current version (in new directories of course) or simply run the Lee’s
> script in the current directories.  I have never had to do this before, so
> would appreciate some help.  Or should I uninstall the current version,
> which is installed from source.
>
> Thanks.
>
> Joe
> VA3JLF
>
>
> Sent from Mail for Windows 10
>
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir