[arch-dev-public] Important changes for all users, developers and TUs
Hi lists, we made some changes to repositories and packages which I'd like to summarize here. 1) (everyone, including users): The current repository is gone. Instead, we have a slimmer core repository and the rest of the packages went to the extra repository. I won't discuss the reasons for that change here, but if necessary, I'd be happy to explain it in a later post. If any packages are missing, don't hesitate to post bug reports. A pacman update will add a /etc/pacman.d/core file and users should change all references in pacman.conf from current to core. We added symlinks for compatibility, so the name current should still work for a while. 2) (everyone, including users): The repository scripts on our server now support the pacman3 style package naming. Our repositories are now partially incompatible with pacman2, as it will fail to find some files. If you haven't updated to pacman3 yet, you can still manually download the libarchive, libdownload and pacman packages from the ftp and install them with pacman2. 3) (users) FTP installations are broken for now, maybe we will have time to fix them soon. Until then, use a base CD to install. 4) (developers and TUs) Related to 1) and 2), a new devtools package has been uploaded. Packages are not renamed any more when uploading. An exception to this is communitypkg, as the community scripts on the server haven't been updated to the pacman3 naming style yet. All devs are encouraged to use the new style names from now on. The currentpkg script is gone, instead there is a corepkg script now, as well as /arch/db-core{,64} on the server. 5) (developers and TUs) The gcc package has been split in gcc and gcc-libs. Packages must not depend on gcc anymore, all those packages should be changed to depend on gcc-libs. This allows us to use C++ applications without forcing users to have gcc installled. Please update your packages as soon as possible. 6) (developers) All former current packages are now in extra or core. We lost the mantainer data for those, so please adopt all packages that were previously yours. This also affects packages which were moved from extra to core. If I forgot anything, tell me. Keep having fun with Arch. Thomas
Thomas Bächler schrieb:
If I forgot anything, tell me. Keep having fun with Arch. Thomas
See, I knew I'd forget something: We should enforce a strict policy on core: If any dev adds a package to core or makes a major change to a package in core, he MUST notify the mailing list. Packages must only be submitted to core if they are either required for installation or first boot, or may be necessary to get network up and running after the initial installation, so that pacman can do its job.
Sunday 16 September 2007, Thomas Bächler wrote: | Thomas Bächler schrieb: | > If I forgot anything, tell me. | > Keep having fun with Arch. | > Thomas | | See, I knew I'd forget something: | | We should enforce a strict policy on core: If any dev adds a | package to core or makes a major change to a package in core, he | MUST notify the mailing list. | | Packages must only be submitted to core if they are either | required for installation or first boot, or may be necessary to | get network up and running after the initial installation, so that | pacman can do its job. where is the original message by Thomas Bächler? i seem not to have got it in the first place. i have on users and dev-public this as the top-post of this thread. can anybody summarise the changes that happened this weekend? or is this exactly the content of this message i didn't get? thanx + greetings, Damir
Monday 17 September 2007, Damir Perisa wrote: | where is the original message by Thomas Bächler? i seem not to | have got it in the first place. i have on users and dev-public | this as the top-post of this thread. http://archlinux.org/pipermail/arch/2007-September/015430.html i found it on the internet, never mind, - D
On Sun, 16 Sep 2007 15:23:01 +0200
Thomas Bächler
Hi lists,
we made some changes to repositories and packages which I'd like to summarize here.
1) (everyone, including users): The current repository is gone. Instead, we have a slimmer core repository and the rest of the packages went to the extra repository. I won't discuss the reasons for that change here, but if necessary, I'd be happy to explain it in a later post. If any packages are missing, don't hesitate to post bug reports. A pacman update will add a /etc/pacman.d/core file and users should change all references in pacman.conf from current to core. We added symlinks for compatibility, so the name current should still work for a while.
2) (everyone, including users): The repository scripts on our server now support the pacman3 style package naming. Our repositories are now partially incompatible with pacman2, as it will fail to find some files. If you haven't updated to pacman3 yet, you can still manually download the libarchive, libdownload and pacman packages from the ftp and install them with pacman2.
3) (users) FTP installations are broken for now, maybe we will have time to fix them soon. Until then, use a base CD to install.
4) (developers and TUs) Related to 1) and 2), a new devtools package has been uploaded. Packages are not renamed any more when uploading. An exception to this is communitypkg, as the community scripts on the server haven't been updated to the pacman3 naming style yet. All devs are encouraged to use the new style names from now on. The currentpkg script is gone, instead there is a corepkg script now, as well as /arch/db-core{,64} on the server.
5) (developers and TUs) The gcc package has been split in gcc and gcc-libs. Packages must not depend on gcc anymore, all those packages should be changed to depend on gcc-libs. This allows us to use C++ applications without forcing users to have gcc installled. Please update your packages as soon as possible.
6) (developers) All former current packages are now in extra or core. We lost the mantainer data for those, so please adopt all packages that were previously yours. This also affects packages which were moved from extra to core.
If I forgot anything, tell me. Keep having fun with Arch. Thomas
Two more points - 1. (devs) those of you running cvs update in your [extra] repository may notice a ton of "file or directory not found" error messages that won't go away on subsequent updates - these seem to be things that were moved out of extra and into core. I don't know if CVS has an option to remove these, but I just ran rm -r system/{bcm43xx-fwcutter,fuse,ntfs-3g,ntfsprogs} network/{zd1211-firmware,wlan-ng26-utils,wlan-ng26,vpnc,rt2500,openswan,ndiswrapper-utils,ndiswrapper,madwifi-utils,madwifi,iwlwifi-4965-ucode,iwlwifi-3945-ucode,iwlwifi,ipw3945d,ipw3945-ucode,ipw3945,ipw2200-fw,ipw2100-fw,capi4k-utils} and that got rid of 'em. 2. (devs and tus) Secondly, I've attached a plain-text list of all apps in [extra] and [community] that depend on GCC - please check these deps, and ensure that they now depend on gcc-libs, unless for some obscure reason they really do need the gcc compiler. -- Travis
Thomas Bächler schrieb:
5) (developers and TUs) The gcc package has been split in gcc and gcc-libs. Packages must not depend on gcc anymore, all those packages should be changed to depend on gcc-libs. This allows us to use C++ applications without forcing users to have gcc installled. Please update your packages as soon as possible.
Related to that: There are lots of packages that depend on libstdc++5 while they shouldn't. Just a reminder: The only packages that should depend on libstdc++5 are closed-source C++ programs that have been compiled with gcc 3.3 or earlier. Any newer program or any program that is open source (and you compile it yourself) will link against libstdc++.so.6 (NOT .5) and only need gcc-libs as a dependency. Please check your packages: extra/network/d4x/PKGBUILD - not needed extra/network/bincimap/PKGBUILD - same extra/system/gcc3/PKGBUILD - this one needs it extra/system/jre/PKGBUILD - closed source, may need it extra/system/gcc34/PKGBUILD - same as for gcc3 extra/system/filelight/PKGBUILD - I am fixing this now extra/modules/fglrx-utils/PKGBUILD - closed source, may need it community/emulators/virtualbox-ose-additions/PKGBUILD community/emulators/virtualbox-ose/PKGBUILD community /modules/virtualbox-ose-additions-modules/PKGBUILD community/x11/virtualbox-ose-xorg-drivers/PKGBUILD These have it as a makedep, which I think is weird community/x11/sancho-gtk/PKGBUILD -- dep libstdc++5 community/network/mldonkey/PKGBUILD -- dep libstdc++5 community/network/sopcast/PKGBUILD -- dep libstdc++5 community/network/mysqlcc/PKGBUILD -- dep libstdc++5 community/network/flock/PKGBUILD -- dep libstdc++5 community/gnome/gnome-cups-manager/PKGBUILD -- dep libstdc++5 community/system/acpitool/PKGBUILD -- dep libstdc++5 community/devel/openthreads/PKGBUILD -- dep libstdc++5 community/devel/sqlitebrowser/PKGBUILD -- dep libstdc++5 I don't think any of these needs it, please fix that.
On Sun, 16 Sep 2007 19:59:23 +0200
Thomas Bächler
extra/modules/fglrx-utils/PKGBUILD - closed source, may need it
Yeah, it does - or at least it has since we moved to libstdc++6 - I haven't checked recently to see if it's been compiled against the newer version. I'll give it a look. -- Travis
participants (3)
-
Damir Perisa
-
Thomas Bächler
-
Travis Willard