On Fri, Feb 8, 2013 at 3:54 PM, Oon-Ee Ng <ngoonee.talk@xxxxxxxxx> wrote: > On Fri, Feb 8, 2013 at 12:29 PM, Gaetan Bisson <bisson@xxxxxxxxxxxxx> wrote: >> [2013-02-08 15:28:06 +1100] Gaetan Bisson: >>> [2013-02-08 12:14:25 +0800] Oon-Ee Ng: >>> > So I'm checking out python-sympy for some calculations in the Robotics >>> > subject I teach and realized that a bug was recently fixed in git >>> > which is crucial to what I hope to use it for. python-sympy-git in the >>> > AUR and that's settled. >>> > >>> > Then I got to wondering, I only really want to use the -git version >>> > till the next release, but since python-sympy is no longer installed >>> > (conflicts) I wouldn't automatically get it unless I check every once >>> > in a while if version is > 0.7.2. >>> > >>> > I figured installing a blank package with nothing in package() named >>> > python-sympy and with version 0.7.2 would allow me to get notified >>> > when python-sympy-0.7.3 or later gets in the repos. Is this a good way >>> > of doing it, or are there better ways? >>> >>> I would take python-sympy-git's PKGBUILD, replace its pkgname by >>> python-sympy and its pkgver by 0.7.2git20130208. Build and install. >> ^ >> That's a 3. Well, you get the idea. > > I do get the idea, but now that I'm trying it out I realize that > makepkg automatically replaces pkgver with the pkgver detected from > git.... =) maybe it'd be easier for me to modify the final package > instead (just change pkgver in .PKGINFO right?)? I just changed the pkver in the PKGBUILD and did a makepkg -R, that seems to work.
