![](https://secure.gravatar.com/avatar/10a3ceea7f0886152bd6ee6fb28b3579.jpg?s=120&d=mm&r=g)
I noticed that sip just moved rpm2targz to core because libstdc++-compat needs it. However, $ prt-get dependent --all libstdc++-compat libstdc++-compat acroread Since acroread isn't in core, what's libstdc++-compat doing there? I personally deselect it during installation and have never found a need/use for it. On a side node, it'd be cool if a Reply-To: crux-devel@lists.crux.nu header were added to the crux-commits list :)
![](https://secure.gravatar.com/avatar/5fbfdcc9fece431e1ca05e46e42255d6.jpg?s=120&d=mm&r=g)
On Tue, Jul 11, 2006 at 05:25:58PM +0200, Mark Rosenstand wrote:
I noticed that sip just moved rpm2targz to core because libstdc++-compat needs it. However,
Sorry, that's my fault. I've added the rpm2targz dep with commit http://crux.nu/svnweb/CRUX/revision?rev=461, don't ask me why. Anyway, it's nonsense because libstdc++-compat depends on nothing. Greetings Jürgen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
![](https://secure.gravatar.com/avatar/10a3ceea7f0886152bd6ee6fb28b3579.jpg?s=120&d=mm&r=g)
On Tue, 2006-07-11 at 21:03 +0200, Juergen Daubert wrote:
On Tue, Jul 11, 2006 at 05:25:58PM +0200, Mark Rosenstand wrote:
I noticed that sip just moved rpm2targz to core because libstdc++-compat needs it. However,
Sorry, that's my fault. I've added the rpm2targz dep with commit http://crux.nu/svnweb/CRUX/revision?rev=461, don't ask me why. Anyway, it's nonsense because libstdc++-compat depends on nothing.
Shame on you :) Still, are either really core material for 2.3?
![](https://secure.gravatar.com/avatar/5fbfdcc9fece431e1ca05e46e42255d6.jpg?s=120&d=mm&r=g)
On Wed, Jul 12, 2006 at 05:30:10AM +0200, Mark Rosenstand wrote:
On Tue, 2006-07-11 at 21:03 +0200, Juergen Daubert wrote:
On Tue, Jul 11, 2006 at 05:25:58PM +0200, Mark Rosenstand wrote:
I noticed that sip just moved rpm2targz to core because libstdc++-compat needs it. However,
Sorry, that's my fault. I've added the rpm2targz dep with commit http://crux.nu/svnweb/CRUX/revision?rev=461, don't ask me why. Anyway, it's nonsense because libstdc++-compat depends on nothing.
Shame on you :)
Still, are either really core material for 2.3?
Depends on. If we have an incompatible gcc change libstdc++-compat is important if you update your system, because every C++ app, compiled with the old gcc, will not run or even segfault without it. We had such a change with the transition 2.0 -> 2.1, libstdc++.so.5.0.6 comes from CRUX 2.0. -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
participants (2)
-
Juergen Daubert
-
Mark Rosenstand