On Mon, Apr 24, 2017 at 7:39 PM, Rafal Luzynski <digitalfreak@xxxxxxxxxxxxxxxxx> wrote: > 23.04.2017 19:23 Christopher <ctubbsii@xxxxxxxxxxxxxxxxx> wrote: >> >> You can set the name of the file via the GitHub API when you download it. >> >> For jQuery (packaged as js-jquery), I use: >> https://github.com/jquery/jquery/archive/%{version}/jquery-%{version}.tar.gz >> >> This will work for any GitHub project which tags released versions: >> >> https://github.com/<user-or-group>/<repo>/archive/<tag-commit-or-branch>/<preferred-file-name>.tar.gz >> [...] > > I'm afraid this will not work because (according to the GitHub > repo) this project has 0 release tags. Also the archive has been > created only 23 days ago. Isn't it too early to package a project > which has not yet ever been released upstream? Been there, done that. It assumes that other people are following your own model of how source control or product releases work. > Also: > >> [...] >> On Sun, Apr 23, 2017 at 11:38 AM Globe Trotter <itsme_410@xxxxxxxxx >> mailto:itsme_410@xxxxxxxxx > wrote: >> >> > I am trying to package the following from github for fedora. (Actually, I >> > have been using my own RPM for years so it is hopefully not a major task). >> > > > If you say you have been using your own RPM file for this project > for years then maybe the project is not as young as this GitHub > repo suggests? Maybe it's just been imported incorrectly, without > the full history and tags, maybe it has another proper source > repo which should be used instead? I could believe there's another repo for source code. I personally run into this all the time with python and various small perl and java tools. I'll note that it is not "incorrect" to import a project without full history and logs. True, it discards history. But when the history has been in a source control system that does not allow discarding *anything*, much like Subversion tries, it's quite common to create a new git repo with an export and import operation and discard confusing or even copyright violating or internal security burdened content wholesale. And if the link to the old repository is deliberately broke, it massively reduces the risks of accidentally re-importing bulky or inappropriate old material to the new repository. Again, been there, done that. > Regards, > > Rafal > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
