Re: [aur-general] Initial manual cleanup
Renaming packages is no longer necessary. In fact, the scripts require the arch in the package now. You're using the same scripts which run the official repos, so they should do things correctly. Note that existing packages are fine, but all packages in the future MUST have the arch in the package name On Jul 17, 2009 6:25 PM, "Evangelos Foutras" <foutrelis@gmail.com> wrote: Aaron Griffin wrote: > > In the future, mails like this will be autogenerated and sent to the > arch... Hi, Does this script also rename packages to remove the architecture part? I'm asking because I'm seeing quite a few packages that still retain that part: [foutrelis@sigurd i686]$ ls -1|grep i686 amaya-11.2-2-i686.pkg.tar.gz drupal-6.13-1-i686.pkg.tar.gz evas-svn-41104-2-i686.pkg.tar.gz freedroidrpg-0.12.1-1-i686.pkg.tar.gz frostwire-4.18.0-2-i686.pkg.tar.gz gnote-0.5.3-1-i686.pkg.tar.gz gwget-1.0.2-1-i686.pkg.tar.gz haskell-x11-xft-0.3-5-i686.pkg.tar.gz lesspipe-1.70-1-i686.pkg.tar.gz libmatchbox-1.9-2-i686.pkg.tar.gz matchbox-panel-0.9.3-3-i686.pkg.tar.gz matchbox-window-manager-1.2-1-i686.pkg.tar.gz perl-array-compare-1.18-1-i686.pkg.tar.gz rapidsvn-0.10.0-1-i686.pkg.tar.gz ruby-libart-0.19.0-2.1-i686.pkg.tar.gz synce-kde-0.14-1-i686.pkg.tar.gz synce-librapi-0.14-1-i686.pkg.tar.gz synce-libsynce-0.14-1-i686.pkg.tar.gz synce-rra-0.14-1-i686.pkg.tar.gz unshield-0.6-1-i686.pkg.tar.gz xf4vnc-xvnc-20090715-2-i686.pkg.tar.gz
On Sat, Jul 18, 2009 at 2:32 AM, Aaron Griffin<aaronmgriffin@gmail.com> wrote:
Renaming packages is no longer necessary. In fact, the scripts require the arch in the package now. You're using the same scripts which run the official repos, so they should do things correctly.
Note that existing packages are fine, but all packages in the future MUST have the arch in the package name
Sweet. Thanks for the quick reply.
On Fri, 17 Jul 2009 16:32:12 -0700 Aaron Griffin <aaronmgriffin@gmail.com> wrote:
Renaming packages is no longer necessary. In fact, the scripts require the arch in the package now. You're using the same scripts which run the official repos, so they should do things correctly.
Note that existing packages are fine, but all packages in the future MUST have the arch in the package name
How are packages for "any" architecture currently handled? Are they duplicated for each architecture-specific repo?
participants (3)
-
Aaron Griffin
-
Evangelos Foutras
-
Xyne