On 28/09/05, Mark Rosenstand <[EMAIL PROTECTED]> wrote:
> I've made a feature wishlist for pacman. I'd like to hear your comments!
>
> 1. Option to fake %REASON% when --add'ing packages.
>
>    This is handy, for example, if you're installing $makedepend'ed packages
>    or a chain of home made packages (e.g., libgalago in order to install
>    galago-daemon) and don't want the dependencies to be kept after removing.
>
> 2. Deprecation of -Qe in favour of better alternatives:
>
>    a) Query option to list all packages that were installed as dependencies 
> but
>       are no longer depended upon by any installed package.
>       Like a global -Rn, but only querying. Removing will probably be to point
>       revolvers at too many people's feet.
>
>    b) Query option to list all explicitly installed packages, whether depended
>       upon by other packages or not. This will reduce the amount of boringness
>       associated with cleaning out packages, as you won't have to re-read the
>       output of -Qe every time you remove a package because it had unwanted
>       dependencies which were also explicitly installed.
>
> 3. Sync option to remove package tarballs for packages not installed on the
>    system.
>
>    With the current cleaning options (-c), trying out fooapp and deciding that
>    it sucks will keep /var/cache/pacman/pkg/fooapp-1.0.pkg.tar.gz until a new
>    version of fooapp are in the repos. Since fooapp 1.0 sucks, I probably 
> won't
>    install it again, and if people tell me that 1.1 kicks ass I'll have to do 
> a
>    download anyway.
>
> 4. Declaration of post_install() and friends inside PKGBUILDs.
>
>    It seems silly that you're declaring a build() function but need an 
> external
>    file to declare other basic functions. I do realize that it's easier to
>    include the file with install time functions in the tarball, but it
>    shouldn't be too hard to extract them from the PKGBUILD and then include.
>
>    It's also silly that you have to write the same three lines at the buttom
>    of every single install-file.

5. Change makepkg to automatically make two packages -- one with the
program and one with the documentation; add a pacman.conf option to
automatically install the documentation when installing a package --
for those of use who like application x's help menu to actually do
something... (see earlier discussions on this list).

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to