Hi everyone, As time has allowed, I have been taking a look at pulling together a "snap" package of JPilot to make installation of the app easier for end users. As I have had a discussion with some experienced snap builders, they have indicated that the best path forward would be to take advantage of the toolset built into snap that utilizes a connection with github to build the package directly from the code in the repository. With this in mind, I'd like to know a little more about the github setup for the JPilot project. Are the dependencies (libpisock, pilot-link, etc.) included in the main repository? If so, I could see this being a challenge since we'd need to be able to separate them and figure out how to build them into the snap since they are not in the Ubuntu repositories. Thanks, Jon

Hi, We could go down that road, but it sounds like overkill and a lot of work.  I like the idea of a build system and getting the build process automated. I uploaded the packages I built to this packagecloud repo and it was really easy.  If we decide to go this route we would still need to document the build process or automate it on github or package cloud has a CI/CD system. This works for Ubuntu 20.04: curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh | sudo bash sudo apt install jpilot jpilot-plugins It should be easy to make it work for 22.04, Debian and RPM based systems if someone builds the rpm. Feedback welcome. Judd On 5/30/22 21:44, Jon Reagan wrote: > Hi everyone, > > As time has allowed, I have been taking a look at pulling together a "snap" package of JPilot to make installation of the app easier for end users. As I have had a discussion with some experienced snap builders, they have indicated that the best path forward would be to take advantage of the toolset built into snap that utilizes a connection with github to build the package directly from the code in the repository. > > With this in mind, I'd like to know a little more about the github setup for the JPilot project. Are the dependencies (libpisock, pilot-link, etc.) included in the main repository? If so, I could see this being a challenge since we'd need to be able to separate them and figure out how to build them into the snap since they are not in the Ubuntu repositories. > > Thanks, > Jon > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org

This should now work for Ubuntu 20.04 and 22.04: curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh | sudo bash sudo apt install jpilot jpilot-plugins Judd On 5/31/22 00:16, Judd Montgomery wrote: > Hi, > > We could go down that road, but it sounds like overkill and a lot of > work.  I like the idea of a build system and getting the build process > automated. > > I uploaded the packages I built to this packagecloud repo and it was > really easy.  If we decide to go this route we would still need to > document the build process or automate it on github or package cloud > has a CI/CD system. > > This works for Ubuntu 20.04: > > curl -s > https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh > | sudo bash > sudo apt install jpilot jpilot-plugins > > It should be easy to make it work for 22.04, Debian and RPM based > systems if someone builds the rpm. > > Feedback welcome. > > Judd > > > On 5/30/22 21:44, Jon Reagan wrote: >> Hi everyone, >> >> As time has allowed, I have been taking a look at pulling together a >> "snap" package of JPilot to make installation of the app easier for >> end users.  As I have had a discussion with some experienced snap >> builders, they have indicated that the best path forward would be to >> take advantage of the toolset built into snap that utilizes a >> connection with github to build the package directly from the code in >> the repository. >> >> With this in mind, I'd like to know a little more about the github >> setup for the JPilot project.  Are the dependencies (libpisock, >> pilot-link, etc.) included in the main repository? If so, I could see >> this being a challenge since we'd need to be able to separate them >> and figure out how to build them into the snap since they are not in >> the Ubuntu repositories. >> >> Thanks, >> Jon >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org

That's great, Judd! I look forward to spinning up a VM and giving the new repo a test. Thanks, Jon ________________________________ From: Judd Montgomery <judd@jpilot.org> Sent: Tuesday, May 31, 2022 12:44 AM To: jpilot@lists.jpilot.org <jpilot@lists.jpilot.org> Subject: [jp] Re: Snap Development This should now work for Ubuntu 20.04 and 22.04: curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh | sudo bash sudo apt install jpilot jpilot-plugins Judd On 5/31/22 00:16, Judd Montgomery wrote: > Hi, > > We could go down that road, but it sounds like overkill and a lot of > work. I like the idea of a build system and getting the build process > automated. > > I uploaded the packages I built to this packagecloud repo and it was > really easy. If we decide to go this route we would still need to > document the build process or automate it on github or package cloud > has a CI/CD system. > > This works for Ubuntu 20.04: > > curl -s > https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh > | sudo bash > sudo apt install jpilot jpilot-plugins > > It should be easy to make it work for 22.04, Debian and RPM based > systems if someone builds the rpm. > > Feedback welcome. > > Judd > > > On 5/30/22 21:44, Jon Reagan wrote: >> Hi everyone, >> >> As time has allowed, I have been taking a look at pulling together a >> "snap" package of JPilot to make installation of the app easier for >> end users. As I have had a discussion with some experienced snap >> builders, they have indicated that the best path forward would be to >> take advantage of the toolset built into snap that utilizes a >> connection with github to build the package directly from the code in >> the repository. >> >> With this in mind, I'd like to know a little more about the github >> setup for the JPilot project. Are the dependencies (libpisock, >> pilot-link, etc.) included in the main repository? If so, I could see >> this being a challenge since we'd need to be able to separate them >> and figure out how to build them into the snap since they are not in >> the Ubuntu repositories. >> >> Thanks, >> Jon >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org _______________________________________________ Jpilot mailing list -- jpilot@lists.jpilot.org To unsubscribe send an email to jpilot-leave@lists.jpilot.org