[suggest] git-svn has subversion-1.4.2 dependency only

[Brandon Ooi]

Git in rpmforge is at a very modern 1.7.3.4 and subversion at a modern
1.6.15 but the git-svn package seems to depend on subversion-1.4.2 only
making it impossible to install the git, subversion and git-svn RF packages
together.

Any way we can get git-svn to link against the RF subversion package?

Thanks!

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.repoforge.org/pipermail/users/attachments/20110207/f191cc02/attachment.html

[Yury V. Zaytsev]

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)

Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?

Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)
Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?
Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

But that fails to work with my current (static) buildsystem setup. One
more reason to move away from it :-)

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)
Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?
Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

But that fails to work with my current (static) buildsystem setup. One
more reason to move away from it :-)

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)
Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?
Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

But that fails to work with my current (static) buildsystem setup. One
more reason to move away from it :-)

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)
Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?
Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

But that fails to work with my current (static) buildsystem setup. One
more reason to move away from it :-)

[Dag Wieers]

Post by Yury V. Zaytsev

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)
Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?
Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

But that fails to work with my current (static) buildsystem setup. One
more reason to move away from it :-)

[Brandon Ooi]

Git in rpmforge is at a very modern 1.7.3.4 and subversion at a modern
1.6.15 but the git-svn package seems to depend on subversion-1.4.2 only
making it impossible to install the git, subversion and git-svn RF packages
together.

Any way we can get git-svn to link against the RF subversion package?

Thanks!

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.repoforge.org/pipermail/users/attachments/20110207/f191cc02/attachment-0001.html

[Yury V. Zaytsev]

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)

Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?

Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

[Brandon Ooi]

Git in rpmforge is at a very modern 1.7.3.4 and subversion at a modern
1.6.15 but the git-svn package seems to depend on subversion-1.4.2 only
making it impossible to install the git, subversion and git-svn RF packages
together.

Any way we can get git-svn to link against the RF subversion package?

Thanks!

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.repoforge.org/pipermail/users/attachments/20110207/f191cc02/attachment-0002.html

[Yury V. Zaytsev]

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)

Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?

Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

[Brandon Ooi]

Git in rpmforge is at a very modern 1.7.3.4 and subversion at a modern
1.6.15 but the git-svn package seems to depend on subversion-1.4.2 only
making it impossible to install the git, subversion and git-svn RF packages
together.

Any way we can get git-svn to link against the RF subversion package?

Thanks!

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.repoforge.org/pipermail/users/attachments/20110207/f191cc02/attachment-0003.html

[Yury V. Zaytsev]

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)

Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?

Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...

[Brandon Ooi]

Git in rpmforge is at a very modern 1.7.3.4 and subversion at a modern
1.6.15 but the git-svn package seems to depend on subversion-1.4.2 only
making it impossible to install the git, subversion and git-svn RF packages
together.

Any way we can get git-svn to link against the RF subversion package?

Thanks!

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.repoforge.org/pipermail/users/attachments/20110207/f191cc02/attachment-0004.html>

[Yury V. Zaytsev]

Post by Brandon Ooi
Any way we can get git-svn to link against the RF subversion package?

That's true, but I wonder if it's even necessary. Git is in rpmforge and
updated subversion is in rpmforge-extras. Right now, it doesn't require
extras to be enabled to install which is a good thing (tm)

Maybe we should build two versions of git, one in main and one in extras
linked to different versions of subversion? And add say "m" and "x" to
the version tags so that extras would override the main one if extras
repository is enabled?

Only this would mean that 2 SPECs have to be kept in sync which is not
complicated, but could be prone to manual errors...