@mnovick1988, done.
Search Criteria
Package Details: dcron 4.5-8
| Git Clone URL: | https://aur.archlinux.org/dcron.git (read-only) |
|---|---|
| Package Base: | dcron |
| Description: | dillon's lightweight cron daemon |
| Upstream URL: | http://www.jimpryor.net/linux/dcron.html |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | xyproto |
| Maintainer: | x33a |
| Last Packager: | x33a |
| Votes: | 32 |
| Popularity: | 0.008403 |
| First Submitted: | 2013-01-24 14:33 |
| Last Updated: | 2016-02-15 06:41 |
Dependencies (2)
- bash (bash-devel-git)
- msmtp-mta (optional) – sending cron job output via email
Required by (15)
- aegir (requires cron)
- backintime-cli (requires cron)
- backintime-cli-git (requires cron)
- gitodo-git (requires cron) (optional)
- gophcatch-git (requires cron) (optional)
- logrotate-nosystemd (requires cron) (optional)
- lone-tar (requires cron)
- mu (requires cron) (optional)
- netkit-rwho-debian (requires cron) (optional)
- openssh-known-hosts (requires cron) (optional)
- pkgupdate-git (requires cron)
- pulledpork (requires cron)
- timeshift (requires cron)
- tuptime (requires cron)
- update-dnsomatic (requires cron) (optional)
Sources (2)
Latest Comments
x33a commented on 2016-02-15 06:44
mnovick1988 commented on 2016-02-14 04:35
please add armv7h, as well. (RPI-2)
x33a commented on 2015-06-17 11:06
Updated PKGBUILD. Now it explicitly mentions armv6h instead of any.
Thanks all.
giddie commented on 2015-06-17 10:58
Oh yeah, sorry: I think I misunderstood your question. Yeah, it shouldn't be a problem to do this on the AUR, as the AUR isn't officially supported anyway, so I'd say we're free to put whatever we like in arch. I've done this for a couple of my packages.
x33a commented on 2015-06-17 10:58
Yes, I know about the syntax. But I was thinking about the guidelines. But apparently, it is fine to include other architectures in AUR packages since AUR is unsupported as a whole.
Reference: https://bbs.archlinux.org/viewtopic.php?id=160737
giddie commented on 2015-06-17 10:56
It should be an array, like this:
arch=('i686' 'x86_64' 'armv6h')
x33a commented on 2015-06-17 10:54
Thanks guys for the explanation. So, would it be fine if I put armv6h in the PKGBUILD, since Arch doesn't officially support anything other than i686 and x86_64?
giddie commented on 2015-06-17 10:52
The arch field doesn't describe the code; it describes the *package*. Once the package is built, it will declare "arch=any", but that's not the case: it contains a compiled binary, which ties it to a specific architecture.
If I understand correctly, makepkg will choose the build arch from the list in the PKGBUILD, and that arch will be used for the package metadata. Using "any" in the PKGBUILD means that the package will be marked as suitable for "any", which is misleading.
JonnyJD commented on 2015-06-17 10:52
@x33a:
running namcap on the any.pkg.tar.xz gives:
dcron E: ELF file ('usr/sbin/crond') found in an 'any' package.
dcron E: ELF file ('usr/bin/crontab') found in an 'any' package.
JonnyJD commented on 2015-06-17 10:50
@x33a: This is not about archicture specific _code_.
The resulting binary package contains an ELF executable and is different for different architectures. So the binary package is not architecture independent, which is exactly what "any" in the PKGBUILD would mean.