On Fri, Feb 8, 2013 at 12:26 PM, Allan McRae wrote:

On 08/02/13 14:14, Oon-Ee Ng wrote:

...

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?

The other option is to use ABS to build the current python-sympy with the patch you need. Or you could even file a bug report to get that done officially (if the bug is bad enough).

Allan

Nah its nowhere near bad enough, some would call it an enhancement (trigonometric simplification now supports a few more identities, including one that's very common in my application). I thought about this but its more work on my end. Gaetan's suggestion appeals to the lazy ass in me =)

[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.

-- Gaetan

On Fri, Feb 8, 2013 at 3:54 PM, Oon-Ee Ng wrote:

On Fri, Feb 8, 2013 at 12:29 PM, Gaetan Bisson 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.