Aaron is right about communication, so I am posting this here:
While splitting the current/base category into core/base and core/devel, it has been decided to split the gcc package into gcc(tools) and libgcc(libs:libstdc++,libgcc_s,...), so that no package will have to depend on gcc in the future, but rather on libgcc.
gcc will depend on libgcc, gcc will go to core/devel and libgcc will go to core/base.
Jan hopes he can do the split tonight.
On Fri, Sep 14, 2007 at 07:09:30PM +0200, Thomas Bächler wrote:
Aaron is right about communication, so I am posting this here:
While splitting the current/base category into core/base and core/devel, it has been decided to split the gcc package into gcc(tools) and libgcc(libs:libstdc++,libgcc_s,...), so that no package will have to depend on gcc in the future, but rather on libgcc.
gcc will depend on libgcc, gcc will go to core/devel and libgcc will go to core/base.
Jan hopes he can do the split tonight.
Is this something we could do after the migration? I'm just worried about more steps having the potential for more problems.
Jason
On 9/14/07, Jason Chu jason@archlinux.org wrote:
On Fri, Sep 14, 2007 at 07:09:30PM +0200, Thomas Bächler wrote:
Aaron is right about communication, so I am posting this here:
While splitting the current/base category into core/base and core/devel, it has been decided to split the gcc package into gcc(tools) and libgcc(libs:libstdc++,libgcc_s,...), so that no package will have to depend on gcc in the future, but rather on libgcc.
gcc will depend on libgcc, gcc will go to core/devel and libgcc will go to core/base.
Jan hopes he can do the split tonight.
Is this something we could do after the migration? I'm just worried about more steps having the potential for more problems.
I think it should at least go to testing so we can verify the split works out fine for all that stuff... but otherwise, I trust JGC to make the transition smooth.
Am Fri, 14 Sep 2007 12:18:21 -0500 schrieb "Aaron Griffin" aaronmgriffin@gmail.com:
I think it should at least go to testing so we can verify the split works out fine for all that stuff... but otherwise, I trust JGC to make the transition smooth.
thw whole new core repo will stay a kind of testing state for a while. we will also have to fix pacman.conf and some installer fixes.
think we don't need to bring gcc/libgcc to testing first. we will also probably start right with 4.2.2 rc1 that is expected to be released next week.
Andy
Jason Chu schrieb:
Is this something we could do after the migration? I'm just worried about more steps having the potential for more problems.
Jason
It's about keeping the repository clean from the beginning: gcc belongs in core/devel, but the dependencies (like db) would put it into core/base.
I think we should have done that split a long time ago and this is just a good time to do it.
arch-dev-public@lists.archlinux.org