[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 at lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>

_______________________________________________
Xastir mailing list
Xastir at lists.xastir.org
http://xastir.org/mailman/listinfo/xastir