On Sun, Oct 21, 2012 at 01:41:10AM +0100, Stuart Henderson wrote: > On 2012/10/21 01:29, Juan Francisco Cantero Hurtado wrote: > > On Sun, Oct 21, 2012 at 12:02:46AM +0100, Stuart Henderson wrote: > > > On 2012/10/20 23:55, Juan Francisco Cantero Hurtado wrote: > > > > On Mon, Oct 08, 2012 at 04:47:47PM -0600, Aaron Bieber wrote: > > > > > On Mon, Oct 01, 2012 at 04:00:47PM -0400, Jiri B wrote: > > > > > > On Mon, Oct 01, 2012 at 12:43:28PM -0600, Aaron Bieber wrote: > > > > > > > Holla! > > > > > > > > > > > > > > Here a port for luakit ( http://luakit.org ). I am just > > > > > > > submitting this > > > > > > > for testing / advice for now. I want to see if I get get a github > > > > > > > tagged-tarball-release to pull from. > > > > > > > > > > Upstream doesn't seem to keen on adding tarball releases, and I can't > > > > > figure out a way to pull github/<user>/<project>/tarball/<tag>. > > > > > > > > For projects that only uses the autogenerated tarballs of github, you > > > > can use this in the Makefile: > > > > > > > > MASTER_SITES = https://github.com/<user>/<project>/tarball/<tag>/ > > > > > > Don't do this in ports, ask the upstream to create a proper download > > > (which can be hosted by github), or mirror them instead. These tarball > > > URLs are dynamically generated and the files can change if github > > > update git, tar or gzip. > > > > I just wanted to comment what is the correct url for the autogenerated > > tarballs of github. When I was creating the port for hotot, I didn't > > find the info. Finally I ran grep for search a example in the port tree. > > IIRC you'll need some hack with a dummy query string along the lines of > MASTER_SITES=https://github.com/<user>/<project>/tarball/<tag>/?make_a_proper_release_you_slackers= > but in my opinion none of these urls providing dynamically-generated > files are correct to use in MASTER_SITES. > > > Is it acceptable to use two master_sites, the first with the github url > > and the second with a mirror?. > > Just use the mirror, but talk to upstream and ask if they'll make an > actual release first. We have to check hashes against the file that was > originally available when something was ported (there have been plenty > of hacked distribution sites, recently including places like sourceforge > mirrors, so checking hashes is necessary) - it's just not sane to do > this against a file which is generated dynamically. >
Latest version: - now puts configs in xdg - removed FULLPKGNAME from PLIST - only depend on webkit,gtk3
luakit.tgz
Description: application/tar-gz
