You are not logged in.
I am going to start this off with the fact that although I am not an idiot, I do lack the understanding to get this to work if it is even possible under Arch, that and I am new to Arch after only a couple months of use.
The question: Can this .zip from Gimmer (Direct DL) be 'installed'? using dpkg or could the package be created using PKGBUILD or the like?
I have tried with dpkg which exits as the .zip has no metadata for dpkg, it seems as though the the dev's intended the zip to be extracted and Gimmer to be opened directly under a Ubuntu system... or something...
I have not tested this program in a debian based distro to even confirm that it works under ubuntu or the others, however I have contacted Gimmer's support and was told that the download was debian targeted (I also mentioned to them that .zip isn't the proper choice for a linux program)
Now a few buddies and I have developed a strong interest in cryptocurrencies (my interest predates theirs); Myself being the most tech savvy of the bunch has been given that task of optimizing our trade gains, as such I could not help but consider automation, Gimmer being one of the tools i wish to test.
At any rate, using a .zip to package a program for linux to me seems like garbage, and is likely do to the fact that Gimmer seems pretty early on in the dev process as a whole.
So in the meantime I am placing this thread here in the hopes that perhaps one of you knows about this type of circumstance, and could clarify further, as i have found nothing so far that is useful in getting a debian targeted .zip file to run under none debian based distro.
I did try the ridiculous solution of renaming the zip to deb, same exit status, obviously, zip files cant carry the metadata needed, but i was being thorough.
As a final note; I have been looking at the open source alternatives and more, atm i am in the R&D stage of our group effort (mostly R), at this point I am more curious then anything.
Last edited by proxe (2017-12-24 15:47:12)
Offline
If you want help from upstream, you should tone down your disdain for zip format. There is absolutely nothing wrong with distributing a bundle of files in a zip archive. Extract it, and you have the files.
The only issue is that the files that are being distributed in that archive are precompiled binaries. They will only run on machines and OSs sufficiently similar to the one they were compiled on. No amount of fiddling around with archive extensions or metadata will change that.
It would be trivial to package this for arch - I have no idea, however, whether or not these binaries could run on arch, and would not have much hope that they would. But if you try, and you report the errors you get, we might be able to help. But don't expect anyone here to run some unknown precompiled binary from an unknown source for you.
Last edited by Trilby (2017-12-24 03:10:55)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
If you want help from upstream, you should tone down your disdain for zip format. There is absolutely nothing wrong with distributing a bundle of files in a zip archive. Extract it, and you have the files.
The only issue is that the files that are being distributed in that archive are precompiled binaries. They will only run on machines and OSs sufficiently similar to the one they were compiled on. No amount of fiddling around with archive extensions or metadata will change that.
It would be trivial to package this for arch - I have no idea, however, whether or not these binaries could run on arch, and would not have much hope that they would. But if you try, and you report the errors you get, we might be able to help. But don't expect anyone here to run some unknown precompiled binary from an unknown source for you.
Have zero disdain for .zip files, use them all the time, i just don't see it as a proper for distributing programs, is all, i have asked for source, no response as of yet.
Last edited by proxe (2017-12-24 03:22:42)
Offline
The package ships custom versions of libffmpeg, libnode and libnw => "installation" means to extract it into /opt and run it from there.
This is a pretty much self contained semi-static binary release and nothing that should be covered by a package manager.
Offline
The package ships custom versions of libffmpeg, libnode and libnw => "installation" means to extract it into /opt and run it from there.
This is a pretty much self contained semi-static binary release and nothing that should be covered by a package manager.
Thanks seth, lol I feel like an idiot this is fairly obvious.
Offline