You are not logged in.
Having used the AUR for a while, I have seen that nearly all wget source from external site, then make it. I see the advantages in this.
Now, however, I wish to submit a package, but there is no source available. Is there a rule against putting wget "server.com/binary.file" in build section of PKGBUILD, or is it considered bad practice. I'm sure that some of the drivers and kernel modules do this.
All guides are specific to compiling source, yet never explicitly state a rule against precompiled executables.
The file is from a trusted source, so am I OK to submit.
Thanks
Ben
Last edited by ziarkaen (2009-06-22 22:48:25)
ziarkaen
Offline
There is a rule against putting binaries directly into the AUR tarball. It's ok to use a binary archive as a source file in a PKGBUILD, though. Look at practically any lib32-* PKGBUILD. Most of them use the Arch 32-bit package as their source, tearing it apart and repacking it. Some use debs or rpms and then convert them to tar, extract them, and repack them.
Offline
Submitting Packages to UNSUPPORTED
After logging in to the AUR web interface, a user can submit a gzipped tarball (tar.gz) of a directory containing build files for a package. The directory inside the tarball should contain a PKGBUILD, any .install files, patches, etc (ABSOLUTELY no binaries). Examples of what such a directory should look like can be seen inside /var/abs.
... so ixnay on the inbays.
What package do you want to upload? If it's something that you've created, you should find a (free) host to distribute your sources. If it's something that you've found somewhere else, pull what you need from there.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
No, not my own creation.
And yes, I will pull binary from http server, not including it in tarball.
Thanks for clarification
ziarkaen
Offline