Re: [aur-general] How do you deal with pkgver() & version controlled PKGBUILDs?
I asked here because I was hoping perhaps there was some way of disabling makepkg from editing PKGBUILDs. But, thanks for the git based solution; it'll get the job done. Do you happen to know why makepkg needs to update the pkgver variable, if it could just run the pkgver function every time? On Thu, Feb 12, 2015 at 7:22 PM, Ido Rosen wrote: > Since this is a git question, it probably belongs on that project's mailing > list. > > Anyhow, what I do is use git smudge/clean filters to ignore the line. > Here's an example from a different application of smudge/clean filters of > how to ignore specific lines in a file: > > http://stackoverflow.com/questions/16244969/how-to-tell-git-to-ignore-individual-lines-i-e-gitignore-for-specific-lines-of > > On Thu, Feb 12, 2015 at 10:11 PM, Jashandeep Sohi < > jashandeep.s.s...@gmail.com> wrote: > >> Hi, >> >> I'm using git to version control my PKGBUILDs. Most of them build >> stable versions of packages using a static pkgver; however, some of >> them build unstable versions (from git, hg, etc.), and make use of the >> pkgver() function to compute a pkgver on build time. >> >> The problem that I'm having is that whenever I build one of the >> unstable packages, the value of pkgver in the PKGBUILD get updated by >> pkgver(), which causes Git to think that the file has changed. If I >> ever want to commit changes to the PKGBUILD, I first have to change >> pkgver back to what it was to prevent spurious changes to pkgver to >> committed as well. >> >> I know I'm being pedantic, but if someone has already thought of a >> solution/fix, that would appreciated. >> >> Thanks, >> Jashandeep Sohi >>
Re: [aur-general] How do you deal with pkgver() & version controlled PKGBUILDs?
You can use `git add --patch` to add specific portions of a file to the git staging area. git add --patch PKGBUILD git checkout -- PKGBUILD
Re: [aur-general] How do you deal with pkgver() & version controlled PKGBUILDs?
Since this is a git question, it probably belongs on that project's mailing list. Anyhow, what I do is use git smudge/clean filters to ignore the line. Here's an example from a different application of smudge/clean filters of how to ignore specific lines in a file: http://stackoverflow.com/questions/16244969/how-to-tell-git-to-ignore-individual-lines-i-e-gitignore-for-specific-lines-of On Thu, Feb 12, 2015 at 10:11 PM, Jashandeep Sohi < jashandeep.s.s...@gmail.com> wrote: > Hi, > > I'm using git to version control my PKGBUILDs. Most of them build > stable versions of packages using a static pkgver; however, some of > them build unstable versions (from git, hg, etc.), and make use of the > pkgver() function to compute a pkgver on build time. > > The problem that I'm having is that whenever I build one of the > unstable packages, the value of pkgver in the PKGBUILD get updated by > pkgver(), which causes Git to think that the file has changed. If I > ever want to commit changes to the PKGBUILD, I first have to change > pkgver back to what it was to prevent spurious changes to pkgver to > committed as well. > > I know I'm being pedantic, but if someone has already thought of a > solution/fix, that would appreciated. > > Thanks, > Jashandeep Sohi >
[aur-general] How do you deal with pkgver() & version controlled PKGBUILDs?
Hi, I'm using git to version control my PKGBUILDs. Most of them build stable versions of packages using a static pkgver; however, some of them build unstable versions (from git, hg, etc.), and make use of the pkgver() function to compute a pkgver on build time. The problem that I'm having is that whenever I build one of the unstable packages, the value of pkgver in the PKGBUILD get updated by pkgver(), which causes Git to think that the file has changed. If I ever want to commit changes to the PKGBUILD, I first have to change pkgver back to what it was to prevent spurious changes to pkgver to committed as well. I know I'm being pedantic, but if someone has already thought of a solution/fix, that would appreciated. Thanks, Jashandeep Sohi
[aur-general] Signoff report for [community-testing]
=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 0 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 0 fully signed off packages * 20 packages missing signoffs * 1 package older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == Incomplete signoffs for [community] (20 total) == * android-udev-r133-1 (any) 0/2 signoffs * freevo-1.9.0-14 (any) 0/2 signoffs * acpi_call-1.1.0-22 (i686) 0/1 signoffs * bbswitch-0.8-26 (i686) 0/1 signoffs * nodejs-0.12.0-1 (i686) 0/1 signoffs * r8168-8.039.00-10 (i686) 0/1 signoffs * rt3562sta-2.4.1.1_r1-20 (i686) 0/1 signoffs * tp_smapi-0.41-63 (i686) 0/1 signoffs * vhba-module-20140928-6 (i686) 0/1 signoffs * virtualbox-4.3.20-6 (i686) 0/1 signoffs * virtualbox-modules-4.3.20-9 (i686) 0/1 signoffs * acpi_call-1.1.0-22 (x86_64) 0/2 signoffs * bbswitch-0.8-26 (x86_64) 0/2 signoffs * nodejs-0.12.0-1 (x86_64) 0/2 signoffs * r8168-8.039.00-10 (x86_64) 0/2 signoffs * rt3562sta-2.4.1.1_r1-20 (x86_64) 0/2 signoffs * tp_smapi-0.41-63 (x86_64) 0/2 signoffs * vhba-module-20140928-6 (x86_64) 0/2 signoffs * virtualbox-4.3.20-6 (x86_64) 0/2 signoffs * virtualbox-modules-4.3.20-9 (x86_64) 0/2 signoffs == All packages in [community-testing] for more than 14 days (1 total) == * freevo-1.9.0-14 (any), since 2014-08-27 == Top five in signoffs in last 24 hours == 1. bisson - 5 signoffs
