Re: Best practice for mackaging software without "release tarballs"?
On 2014-05-19 08:47, Lev Serebryakov wrote: Problem is, this is NOT a github :) git != github, you know? Roll your own tarball and host it on freefall in your ~/public_distfiles http://www.freebsd.org/doc/en/books/porters-handbook/slow-sources.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Best practice for mackaging software without "release tarballs"?
Hello, Robert. You wrote 19 мая 2014 г., 17:40:39: >> I want to make port for TI MSP430 toolchain (binutils-newlib-gcc based, >> new >> one, not old and unsupported "devel/msp430*"), but problem is, that I need >> to package "tip of git branch", as all released tarballs (even snapshot >> ones) contains bugs. >> >> What is the best practice for such situation? Is it possible to require >> git >> as build-dependency and checkout sources (with some fixed revision, of >> course, not "rolling" one) or should I prepare tarballs myself and put it >> into ${MASTER_SITE_LOCAL}? >> >> If the software has been ported, and the software is on Github, you can RB> specify any git tag and it will download that tag. For instance: RB> USE_GITHUB= yes RB> GH_ACCOUNT= bitcoin RB> GH_PROJECT= bitcoin RB> GH_COMMIT= 4a102fa RB> GH_TAGNAME= ${GH_COMMIT} RB> That said, most persons would prefer you pulled the latest release, and RB> applied necessary bug fixes as patches. Problem is, this is NOT a github :) git != github, you know? -- // Black Lion AKA Lev Serebryakov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Best practice for mackaging software without "release tarballs"?
On 19 May 2014 23:35, Lev Serebryakov wrote: > Hello, Ports. > > I want to make port for TI MSP430 toolchain (binutils-newlib-gcc based, > new > one, not old and unsupported "devel/msp430*"), but problem is, that I need > to package "tip of git branch", as all released tarballs (even snapshot > ones) contains bugs. > > What is the best practice for such situation? Is it possible to require > git > as build-dependency and checkout sources (with some fixed revision, of > course, not "rolling" one) or should I prepare tarballs myself and put it > into ${MASTER_SITE_LOCAL}? > > If the software has been ported, and the software is on Github, you can specify any git tag and it will download that tag. For instance: USE_GITHUB= yes GH_ACCOUNT= bitcoin GH_PROJECT= bitcoin GH_COMMIT= 4a102fa GH_TAGNAME= ${GH_COMMIT} That said, most persons would prefer you pulled the latest release, and applied necessary bug fixes as patches. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Best practice for mackaging software without "release tarballs"?
Hello, Ports. I want to make port for TI MSP430 toolchain (binutils-newlib-gcc based, new one, not old and unsupported "devel/msp430*"), but problem is, that I need to package "tip of git branch", as all released tarballs (even snapshot ones) contains bugs. What is the best practice for such situation? Is it possible to require git as build-dependency and checkout sources (with some fixed revision, of course, not "rolling" one) or should I prepare tarballs myself and put it into ${MASTER_SITE_LOCAL}? -- // Black Lion AKA Lev Serebryakov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"