Re: [Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[Curt Mills]

I believe I was the one who created and maintained the spec.in files, but
for SuSE. I didn't need to change them much over the years I needed them.
Used them to create the RPM's I distributed. I didn't distribute CentOS
RPM's but they can certainly be easily adapted for that.

Curt, WE7U
http://wetnet.net/~we7u
http://www.sarguydigital.com

Git Pull submitted.

--David
KI6ZHD


On 07/09/2016 10:09 AM, David Ranch wrote:

>
> Hey Tom,
>
> If you rilly would like to get git-centric, try forking the project on
>> github, make a branch, make this modification on it, and submit a pull
>> request.
>>
>
> Ok.. I already had a Github account, forked Xastir, did a git clone to get
> the code to my machine, uploaded my SSH key, and now I need to modify the .
> spec.in file, push the change and then I'll figure out how to do do a
> pull to get your the change.  I'm thinking that the Git based version might
> not be appropriate for inclusion for the sources so I'll just update the
> current one to reflect major releases, tracking the correct dependencies,
> etc.
>
> Give me a bit and I'll get that uploaded
>
> --David
> ___
> 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
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

Re: [Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[David Ranch]

Hello Tom,

I'm working on updating my Xastir documentation for Centos here to now 
use Github/Git vs. sf.net/CVS:


http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#19b.xastir

In doing that update, I noticed the current xastir.spec file which is 
seemingly 13 years old (see change log at the end of the file) shows:


   %configure --without-graphicsmagick --with-rtree

  That seems BAD since we know that GraphicsMagick support is 
probably more reliable than say ImageMagick today.


   make(it's using the %{?_smp_mflags} parameter after the "make" 
it to use multi-threaded CPUs - aka -j)



Anyway.. I updated my xastir.spec file to be more Git centric and you 
can use it if you so wish:


http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/xastir.spec

--David


On 07/07/2016 09:31 AM, Tom Russo wrote:

As announced a couple of months ago, Curt and I have been talking about moving
Xastir version control over to github, and discontinuing use of sourceforge
and CVS for hosting the main repository.

There wasn't much feedback from the group about that, and yesterday we went
ahead and did it.  The sourceforge CVS repository is still there, but all
commit access has been locked down and we'll shut down the CVS repo altogether
when we're sure this is all working properly.

We have not yet migrated the issue tracking data from sourceforge to github,
but that is not a high priority as we have not been using the issue tracker
much, and most of the issues that are there have been getting ignored for
years.

We may continue to use Sourceforge for distribution of release tarballs.
In fact, we will almost certainly continue to use Sourceforge for that.

The Xastir wiki and home page have NOT yet been updated to reflect this
move of version control.  It will be.

In the meantime, if you have been using CVS to keep current with Xastir,
you'll have to change.

The short story:

To get a copy of the development repository, you must have git installed
on your system.

To obtain the repo for the first time:
git clone https://github.com/Xastir/Xastir.git

This will create an Xastir subdirectory, and put a clone of the repository
into it as well as checking out the "master" branch of the code into that
working directory.

At this point, your Xastir subdirectory can be used just as you had used
a cvs checkout to build Xastir.

Periodically, you can update the code by "cd"ing into the repo directory
and executing:
   git pull


If you intend to contribute code to the Xastir project, there's going to be
more to learn, but if you were just using CVS to get access to the latest
source, these two commands will be sufficient to get you up to speed, and
correspond very, very roughly to the "cvs checkout" and "cvs update" commands
you were used to.

A new README.GIT file exists in the source tree, just as there had always
been a README.CVS.



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

Re: [Xastir-dev] Fwd: [Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[Tom Russo]

Thanks, Curt, for forwarding my xas...@xastir.org message to xastir-dev,
which I hardly even think about much, since most of the traffic is on the
user group, not the dev group.

Now that Curt has been very busy updating all the README files to translate
CVS commands and repo URLs to their roughly corresponding git counterparts,
I thought I'd take a moment to point out that our transition to github has
made the process of contributing to the Xastir development a bit simpler than
it used to be, should you choose to take advantage of it.

Git is very different from CVS, because of its distributed model, and it makes
possible a better workflow for managing contributions.  Consider this 
old-school way for you to add or fix Xastir code under CVS:

  0) Notice an issue you'd like to work on
  1) Check out the current code from CVS
  2) Do code changes
  3) Run a CVS diff command, and forward the resulting patch to one of the 
 folks who have commit access (almost always Curt).
  4) Wait for that person to review the code, then commit it.
  5) Repeat.

A better approach, using github's "pull request" capability, is now:
  0) Notice an issue
  1) Fork the Xastir repo on github, creating your own copy to which you 
 automatically have all admin rights.
  1a) Clone your forked copy
  2) Create a feature branch in your repo, and make code changes on that branch
  3) Push your new feature branch with your code changes to github.
  4) Issue a "pull request" to the Xastir project.

This enables some Xastir developer with push access to the project to grab
all of your changes, review them, test them, provide feedback, and ultimately
copy your changes (via a git merge operation) into the main branch of the code
for everyone to enjoy.

One of the benefits of doing it this way is that you actually show up in the
project history as the author of the changes, without one of the developers
having to give you credit by mentioning your name in the commit log, or
adding comments to the code to that effect.

Please see https://help.github.com/articles/using-pull-requests/ for
details on the process.  If you think this is something you're likely to do,
then you should definitely read some of the references at the bottom of
README.GIT to help the process go smoothly.  These include things like the
complete "Pro Git" book, guidelines for writing good commit messages, and
managing your git repo so that the project history looks nice and clean to
people who are browsing it (via git log, gitk, or other repo browsers).

Share and Enjoy.

On Thu, Jul 07, 2016 at 11:18:59AM -0700, we recorded a bogon-computron 
collision of the <curt.w...@gmail.com> flavor, containing:
> -- Forwarded message --
> From: Tom Russo <ru...@bogodyn.org>
> Date: Thu, Jul 7, 2016 at 9:31 AM
> Subject: [Xastir] Xastir development source now on github, sourceforge CVS
> now closed to new commits.
> To: xas...@xastir.org
> 
> 
> As announced a couple of months ago, Curt and I have been talking about
> moving
> Xastir version control over to github, and discontinuing use of sourceforge
> and CVS for hosting the main repository.
> 
> There wasn't much feedback from the group about that, and yesterday we went
> ahead and did it.  The sourceforge CVS repository is still there, but all
> commit access has been locked down and we'll shut down the CVS repo
> altogether
> when we're sure this is all working properly.
> 
> We have not yet migrated the issue tracking data from sourceforge to github,
> but that is not a high priority as we have not been using the issue tracker
> much, and most of the issues that are there have been getting ignored for
> years.
> 
> We may continue to use Sourceforge for distribution of release tarballs.
> In fact, we will almost certainly continue to use Sourceforge for that.
> 
> The Xastir wiki and home page have NOT yet been updated to reflect this
> move of version control.  It will be.
> 
> In the meantime, if you have been using CVS to keep current with Xastir,
> you'll have to change.
> 
> The short story:
> 
> To get a copy of the development repository, you must have git installed
> on your system.
> 
> To obtain the repo for the first time:
>git clone https://github.com/Xastir/Xastir.git
> 
> This will create an Xastir subdirectory, and put a clone of the repository
> into it as well as checking out the "master" branch of the code into that
> working directory.
> 
> At this point, your Xastir subdirectory can be used just as you had used
> a cvs checkout to build Xastir.
> 
> Periodically, you can update the code by "cd"ing into the repo directory
> and executing:
>   git pull
> 
> 
> If you intend to contribute code to the Xastir project, there's going to be
> more to learn, but i

Re: [Xastir-dev] [Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[J. Lance Cotton]

Great! Confirmed works.

On Thu, Jul 7, 2016 at 2:21 PM, km5vy Tom Russo  wrote:

> On Thu, Jul 07, 2016 at 01:17:45PM -0600, we recorded a bogon-computron
> collision of the  flavor, containing:
> > On Thu, Jul 07, 2016 at 02:12:10PM -0500, we recorded a bogon-computron
> collision of the  flavor, containing:
> > > Just trying it out -- checked out the repo, bootstrap.sh, ./configure,
> make
> > >
> > > Unfortunately:
> > >
> > > make[2]: *** No rule to make target `README.CVS', needed by `all-am'.
> Stop.
> >
> > OOPS!  Thanks.  I'll fix that.
>
> Fixed.  Do a git pull and it should work now.
>
> I removed README.CVS as an afterthought right *after* testing everything
> out, and Makefile.am actually referenced it.  It references README.GIT
> instead now.
>
> --
> Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
> Tijeras, NM  QRPL#1592 K2#398  SOC#236
> http://kevan.org/brain.cgi?DDTNM
>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
>
>
>
>
>


-- 
J. Lance Cotton, KJ5O
j...@lightningflash.net
http://kj5o.lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat
the cookies.
___
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev

Re: [Xastir-dev] [Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[km5vy Tom Russo]

On Thu, Jul 07, 2016 at 02:12:10PM -0500, we recorded a bogon-computron 
collision of the  flavor, containing:
> Just trying it out -- checked out the repo, bootstrap.sh, ./configure, make
> 
> Unfortunately:
> 
> make[2]: *** No rule to make target `README.CVS', needed by `all-am'.  Stop.

OOPS!  Thanks.  I'll fix that.

> On Thu, Jul 7, 2016 at 1:27 PM, Curt Mills  wrote:
> 
> > On Thu, Jul 7, 2016 at 9:31 AM, Tom Russo  wrote:
> >
> > > As announced a couple of months ago, Curt and I have been talking about
> > > moving
> > > Xastir version control over to github, and discontinuing use of
> > sourceforge
> > > and CVS for hosting the main repository.
> > >
> > > There wasn't much feedback from the group about that, and yesterday we
> > went
> > > ahead and did it.  The sourceforge CVS repository is still there, but all
> > > commit access has been locked down and we'll shut down the CVS repo
> > > altogether
> > > when we're sure this is all working properly.
> > >
> >  ...
> >
> > > The Xastir wiki and home page have NOT yet been updated to reflect this
> > > move of version control.  It will be.
> > >
> >
> > Note: By "we went ahead and did it", Tom really meant that he did the
> > work.  ;-)  Thanks Tom!
> >
> > The main Xastir Wiki page has been updated, as well as the main SourceForge
> > page. I also created a GitHub Wiki page and pointed it back to the
> > Xastir.org website.
> >
> > I encourage those who have created/updated Xastir Wiki pages in the past to
> > update those pages with the new Git commands.
> >
> > --
> > Curt, WE7U
> > http://we7u.wetnet.net
> > http://www.sarguydigital.com
> > ___
> > Xastir-dev mailing list
> > Xastir-dev@lists.xastir.org
> > http://xastir.org/mailman/listinfo/xastir-dev
> >
> 
> 
> 
> -- 
> J. Lance Cotton, KJ5O
> j...@lightningflash.net
> http://kj5o.lightningflash.net
> Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat
> the cookies.

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://kevan.org/brain.cgi?DDTNM
 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]

 


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

Re: [Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[Curt Mills]

On Thu, Jul 7, 2016 at 9:31 AM, Tom Russo  wrote:

> As announced a couple of months ago, Curt and I have been talking about
> moving
> Xastir version control over to github, and discontinuing use of sourceforge
> and CVS for hosting the main repository.
>
> There wasn't much feedback from the group about that, and yesterday we went
> ahead and did it.  The sourceforge CVS repository is still there, but all
> commit access has been locked down and we'll shut down the CVS repo
> altogether
> when we're sure this is all working properly.
>
 ...

> The Xastir wiki and home page have NOT yet been updated to reflect this
> move of version control.  It will be.
>

Note: By "we went ahead and did it", Tom really meant that he did the
work.  ;-)  Thanks Tom!

The main Xastir Wiki page has been updated, as well as the main SourceForge
page. I also created a GitHub Wiki page and pointed it back to the
Xastir.org website.

I encourage those who have created/updated Xastir Wiki pages in the past to
update those pages with the new Git commands.

-- 
Curt, WE7U
http://we7u.wetnet.net
http://www.sarguydigital.com
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir

[Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

[Tom Russo]

As announced a couple of months ago, Curt and I have been talking about moving
Xastir version control over to github, and discontinuing use of sourceforge
and CVS for hosting the main repository.

There wasn't much feedback from the group about that, and yesterday we went
ahead and did it.  The sourceforge CVS repository is still there, but all
commit access has been locked down and we'll shut down the CVS repo altogether
when we're sure this is all working properly.

We have not yet migrated the issue tracking data from sourceforge to github,
but that is not a high priority as we have not been using the issue tracker
much, and most of the issues that are there have been getting ignored for
years.

We may continue to use Sourceforge for distribution of release tarballs.
In fact, we will almost certainly continue to use Sourceforge for that.

The Xastir wiki and home page have NOT yet been updated to reflect this 
move of version control.  It will be.

In the meantime, if you have been using CVS to keep current with Xastir, 
you'll have to change.

The short story:

To get a copy of the development repository, you must have git installed
on your system.

To obtain the repo for the first time:
   git clone https://github.com/Xastir/Xastir.git

This will create an Xastir subdirectory, and put a clone of the repository
into it as well as checking out the "master" branch of the code into that
working directory.

At this point, your Xastir subdirectory can be used just as you had used
a cvs checkout to build Xastir.

Periodically, you can update the code by "cd"ing into the repo directory
and executing:
  git pull


If you intend to contribute code to the Xastir project, there's going to be
more to learn, but if you were just using CVS to get access to the latest
source, these two commands will be sufficient to get you up to speed, and
correspond very, very roughly to the "cvs checkout" and "cvs update" commands
you were used to.

A new README.GIT file exists in the source tree, just as there had always
been a README.CVS. 

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://kevan.org/brain.cgi?DDTNM
 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