On 08:13 Fri 23 Feb , Douglas Soares de Andrade wrote:
Hi guys,
Thanks for the great work with pacman :)
I have been thinking and what about instead of:
==> Generating md5sums for source files
md5sums=('e1bf4b2941249c223efc524151caaadc')
==> Generating sha1sums for source files
sha1sums=('39059c20d7e3b07c552ee9a9a662db7dbc742363')
Why not:
==> Generating md5sums and sha1sums for source files
or
==> Generating checksums for source files
md5sums=('e1bf4b2941249c223efc524151caaadc') sha1sums=('39059c20d7e3b07c552ee9a9a662db7dbc742363')
Im asking this because it would make easier just to pass the mouse in the two lines and paste in the PKGBUILD. (this is what i do)
And in the current behaviour, i have to copy all lines and then paste in the PKGBUILD and then remove what is not needed.
I know its a comestic one, but it would be good.
Thanks
Actually the messages are printed on the stderr and the {sha1,msd5}sums in the stdout, so you can redirect (e.g.) $> makepkg3 -g >> PKGBUILD and then you move the md5/sha1 before build(). You may find this useful (if you already know that... ignore this mail ;) -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User http://www.archlinux.org