Also, for the record, I know the end result will be the same, but it will also take much longer to download the source. I didn't know if a larger download time was worth the same end result (that was my question, really). The answer to that question was: always go for the source when available. Unfortunately, getting the source to make was difficult, and I have other things to do, so I did what I did.
Again, feel free to repackage.
]]>I decided to see if I could make a PKGBUILD to build from source. Unfortunately, it won't build with tcl 8.6 because it uses features that have been deprecated for 10 years and finally removed. I'm not going to start patching the source, so I'm done here.
]]>Building from source is the ideal thing, but if you just want to make something work quickly, there's probably no way around it.
]]>Personally, I would rather just use the smaller files, but figured I should ask if this could cause problems later on for certain individuals.
]]>Quick question:
If I create a file that reads "exec /opt/fv/fv," give it executable privileges, and then then throw the file into the /usr/bin directory, the command runs perfectly fine; however, when I create a symlink with the command "ln -s /opt/fv/fv /usr/bin/fv" the command will not function appropriately (in fact, it will function as if I had cp'd only the fv command, itself, into the /usr/bin directory). Why is this the case?
]]>karol: So I cp'd the files to /opt/fv and the cp'd the command to /usr/bin. That didn't work. =/
gonX: I cannot make a PKGBUILD until I know how to build it on my system first. At least, that's how I'm reading the wiki. Also, is the latter solution a fair way to make an AUR package? I thought that would be "cheating" in a way.
Also, sorry for being new at this. I really am trying to learn.
You don't need to be able to build it to be able to use a PKGBUILD. I suppose it's a bit misleading name. It could be something as simple as this:
pkgname=fits-viewer
pkgver=1.0
pkgrel=1
pkgdesc="NASA FV"
arch=('i686' 'x86_64')
source=fv.zip
build() {
mkdir -p ${pkgdir}/opt/fv
mkdir -p ${pkgdir}/usr/bin
unzip fv.zip -d ${pkgdir}/opt/fv/
ln -s /opt/fv/fv ${pkgdir}/usr/bin/fv
}
.install files are run after the installation, for example if you have to initialize something on install or on uninstallation
The easiest example would be to run something like abs core/linux and check your /var/abs/core/linux directory for the files.
]]>If it requires that specific directory structure, the correct way to install is to put the entire structure under /opt then make a symlink in /usr/bin pointing to the executable. Not a good solution, but when you're dealing with software that's written in Window's style, there's not much else you can do.
Ah. That sounds like what I've gotta do. Thanks.
]]>Would it be poor AUR etiquette to copy the files to /opt/fv/ and then create an executable file "fv" that calls the fv command from that directory? I tried that and it seems to work just fine.
]]>Also, sorry for being new at this. I really am trying to learn.
Nobody expects you to know everything right from the start :-)
]]>gonX: I cannot make a PKGBUILD until I know how to build it on my system first. At least, that's how I'm reading the wiki. Also, is the latter solution a fair way to make an AUR package? I thought that would be "cheating" in a way.
Also, sorry for being new at this. I really am trying to learn.
]]>