I've been using Arch Linux for almost 9 years now and it never occurred to me that there was a way to have makepkg
not put artifacts in the working directory. Thanks @delx, if I would have RTFM here (https://wiki.archlinux.org/index.php/Makepkg#Package_output), I would have found the same answer you gave. And that should work.
Search Criteria
Package Details: mythtv 31+fixes.20210225.b6ddf202-1
Git Clone URL: | https://aur.archlinux.org/mythtv.git (read-only, click to copy) |
---|---|
Package Base: | mythtv |
Description: | A Homebrew PVR project |
Upstream URL: | https://www.mythtv.org/ |
Keywords: | mythtv |
Licenses: | |
Conflicts: | |
Replaces: | |
Submitter: | Barthalion |
Maintainer: | delx |
Last Packager: | delx |
Votes: | 28 |
Popularity: | 0.83 |
First Submitted: | 2018-01-07 17:35 |
Last Updated: | 2021-02-26 11:45 |
Dependencies (57)
- exiv2
- fftw (fftw-mpich, fftw-mpi, fftw-amd)
- jack (jack-git, jack-stub, jack-dbus, jack2-git, jack2)
- lame (lame-svn, lame-altivec)
- libass (libass-git)
- libavc1394
- libbluray (libbluray-git)
- libhdhomerun
- libiec61883
- libpulse (libpulse-bluedio, pulseaudio-pali, libpulse-airplay, pulseaudio-git, libpulse-hsphfpd, pulseaudio-dummy, libpulse-nosystemd, libpulse-nosystemd-git, libpulse-nosystemd-minimal-git)
- libsamplerate (libsamplerate-git, libsamplerate-minimal-git)
- libva (libva-git, libva-hantro-h264-git, intel-media-stack-bin, libva-minimal-git, libva-headless)
- libvdpau (libvdpau-git)
- libvpx (libvpx-1.6, libvpx-full-git, libvpx-git, libvpx-1.7)
- libxinerama (libxinerama-randr-git)
- libxml2 (libxml2-linenum, libxml2-git)
- libxrandr (libxrandr-git)
- qt5-script (qt5-script-git)
- qt5-webkit (qt5-webkit-print, qt5-webkit-git)
- taglib (taglib-git)
- x264 (x264-ymod-git, x264-tmod-git, x264-git)
- x265 (x265-hg)
- git (git-git) (make)
- help2man (help2man-git) (make)
- libcdio (libcdio-git) (make)
- libcec (libcec-git) (make)
- libmariadbclient (libmysqlclient55, mariadb-libs-git, mariadb103-libs, libmysqlclient56, libmysqlclient57, libmysqlclient, mariadb-libs) (make)
- libxml2 (libxml2-linenum, libxml2-git) (make)
- lirc (lirc-irdroid, lirc-git, lirc-devinput) (make)
- perl-dbd-mysql (make)
- perl-io-socket-inet6 (make)
- perl-libwww (make)
- perl-net-upnp (make)
- perl-xml-simple (make)
- perl-xml-xpath (make)
- python-future (make)
- python-lxml (make)
- python-mysqlclient (make)
- python-requests (make)
- python-simplejson (make)
- yasm (yasm-git) (make)
- glew (glew-libepoxy, glew-git, glew-egl-glx) (optional) – for GPU commercial flagging
- libcec (libcec-git) (optional) – for consumer electronics control capabilities
- mariadb (mysql55, mariadb-git, mariadb103, mysql56, mysql57, mysql, percona-server) (optional) – Database-Backend for server deployment
- mariadb-clients (mysql-clients55, mariadb-clients-git, mariadb103-clients, mysql-clients56, mysql-clients57, mysql-clients, percona-server-clients) (optional) – Database-Frontend for client deployment
- perl-dbd-mysql (optional) – Perl bindings
- perl-io-socket-inet6 (optional) – Perl bindings
- perl-libwww (optional) – Perl bindings
- perl-net-upnp (optional) – Perl bindings
- perl-xml-simple (optional) – Perl bindings
- perl-xml-xpath (optional) – Perl bindings
- python-future (optional) – Python bindings
- python-lxml (optional) – Python bindings
- python-mysqlclient (optional) – Python bindings
- python-requests (optional) – Python bindings
- python-requests-cache (optional) – Python bindings
- python-simplejson (optional) – Python bindings
Required by (20)
- hdhomerun_config_gui (optional)
- mythplugins-mytharchive
- mythplugins-mytharchive (make)
- mythplugins-mythbrowser
- mythplugins-mythbrowser (make)
- mythplugins-mythgame (make)
- mythplugins-mythgame
- mythplugins-mythmusic (make)
- mythplugins-mythmusic
- mythplugins-mythnetvision
- mythplugins-mythnetvision (make)
- mythplugins-mythnews
- mythplugins-mythnews (make)
- mythplugins-mythweather (make)
- mythplugins-mythweather
- mythplugins-mythweb (make)
- mythplugins-mythweb
- mythplugins-mythzoneminder
- mythplugins-mythzoneminder (make)
- nuvexport
Sources (7)
bigcajun826 commented on 2021-02-27 15:05
delx commented on 2021-02-27 10:29
Hi @bigcajun826. You may want to have a look at the BUILDDIR
, PKGDEST
and SRCDEST
options in either /etc/makepkg.conf
or ~/.makepkg.conf
.
This will let you control where files for all packages, no need for a .gitignore
in each package. Does that solve your problem? :)
bigcajun826 commented on 2021-02-26 15:56
@delx
Would you mind adding a .gitignore
file to the source to ignore artifacts of the build? I believe this would be sufficient:
https://github.com/emerkle826/mythtv/blob/gitingnore/.gitignore
delx commented on 2020-11-01 11:46
@mark.clegg Ah, I didn't notice that the old package had epoch=1. This just means people will need to manually upgrade one time to switch to the new version. I think I'll leave it like that.
@jfabernathy I plan to modify this package to track fixes/32 after MythTV v32 is released. If you want to keep tracking fixes/31 you'd need to fork this package, or maintain your own copy locally.
That version number looks fine to me. It's generated using git-describe. This shows you the number of commits since the v31 tag, followed by 'g' and then the commit hash.
jfabernathy commented on 2020-10-30 21:04
I "upgraded" by "yay -S mythtv Pacman.log says: [2020-10-30T16:31:08-0400] [ALPM] removed mythtv-git (31+fixes.20201012.eb3c84de-1) [2020-10-30T16:31:08-0400] [ALPM] installed mythtv (31+fixes.20201012.eb3c84de-1) However, when I run mythfrontend and look at information center I see: Mythfrontend version: makepkg (v31.0-118-geb3c84de5f-dirty)
mark.clegg commented on 2020-10-30 18:46
Just "upgraded" - Started with a new clone from AUR, built and installed without issues. Just one observation, when installing, pacman thought I was "downgrading" the existing package, which I'm sure is just because of a syntax difference between the apparent version numbers, and is safe to ignore during this transition.
From pacman.log:
downgraded mythtv (1:31.0-3 -> 31+fixes.20201012.eb3c84de-1)
jfabernathy commented on 2020-10-30 12:47
Since I built my latest mythtv build from mythtv-git to get to a more current build of v31, how do I move over to this mythtv package? My goal is to follow a package that stays on V31 and tracks the latest commits, but not move to v32 ever. To me V32 should be new AUR package.
delx commented on 2020-10-30 11:57
Hi @RuneArch. Sorry but I don't use any of the MythTV plugins so I don't think I'd be a good maintainer for that package. I'm happy to work with any maintainer to help these packages work well together.
delx commented on 2020-10-30 11:55
This package now tracks the MythTV fixes/31 branch. There are quite a few upstream bugfixes since the v31 release.
Thanks to Taijian and all the previous maintainers for their efforts.
Whenever a commit is made by MythTV's git upstream you can rebuild this package without waiting for an update. Please don't flag it as out of date just because there's a new commit. Occasionally I'll push updates manually to stop the version from looking too old. I'll also push updates whenever a packaging change is needed for the build to work.
RuneArch commented on 2020-10-27 13:02
Just to add... are you taking ownership of mythplugins too?
Pinned Comments
delx commented on 2020-10-30 11:55
This package now tracks the MythTV fixes/31 branch. There are quite a few upstream bugfixes since the v31 release.
Thanks to Taijian and all the previous maintainers for their efforts.
Whenever a commit is made by MythTV's git upstream you can rebuild this package without waiting for an update. Please don't flag it as out of date just because there's a new commit. Occasionally I'll push updates manually to stop the version from looking too old. I'll also push updates whenever a packaging change is needed for the build to work.
Taijian commented on 2019-03-09 11:53
Important Note on AUR packages in general:
For AUR packages, you - as the user installing the package - assume the role that a package maintainer has for regular repo packages.
That means that the responsibility to recompile the package whenever a package B that your package depends on changes. For repo packages, maintainers do this for you and re-release the package with an updated build number (e.g. -1 to -2). AUR mainainers will not do this, because there is no change to the PKGBUILD. You need to recompile locally, whenever this happens.