On Nov 22, 2007 2:59 PM, fancris3 wrote:

[~]:: pacman -Ss|wc -l 9521 this its a feature or a bug?

What, that pacman -Ss returns every package? I'm pretty sure that's by design, so it's not a bug. - Hide quoted text -

i have made a build for bsc-beta,i have a line:

make PREFIX=$startdir/pkg/opt/bsc install || return 1

variable its wrong,makepkg make empty pkg and skip "return 1"

make: Nothing to be done for `install'. ==> Tidying install... -> Removing info/doc files... -> Compressing man pages... -> Stripping debugging symbols from binarie ==> Creating package... -> Generating .FILELIST file... -> Generating .PKGINFO file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: bsc-beta (Thu Nov 22 19:

in the stable version this thing is working correct and return an error

==> Removing info/doc files... ==> Compressing man pages... ==> Stripping debugging symbols from libraries... ==> Stripping symbols from binaries... ==> Generating .FILELIST file... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> Generating .PKGINFO file... ==> Compressing package... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> ERROR: Failed to create package file.

That's a bugfix - the previous version is the buggy one. A packager should be able to build empty packages if they want. It's up to you to ensure your package was built correctly.

On Thu, Nov 22, 2007 at 11:37:21PM -0500, Dan McGee wrote:

On Nov 22, 2007 3:12 PM, Travis Willard wrote:

...

On Nov 22, 2007 2:59 PM, fancris3 wrote:

...

[~]:: pacman -Ss|wc -l 9521 this its a feature or a bug?

What, that pacman -Ss returns every package? I'm pretty sure that's by design, so it's not a bug.

Yeah, I'm not sure what you were trying to do here at all- get a line count of packages with their descriptions? Seems like a weird statistic to me...

I see mainly two possible behaviors for "pacman -Ss" : 1) list everything 2) fail and print a help message asking for an argument I don't think the first one is problematic, but maybe he was expecting the second one.

On Fri, 23 Nov 2007 08:51:37 +0200, Xavier wrote:

I see mainly two possible behaviors for "pacman -Ss" : 1) list everything 2) fail and print a help message asking for an argument I don't think the first one is problematic, but maybe he was expecting the second one.

yes,i expect the second because of pacman.pot : #: src/pacman/pacman.c:562 msgid "no targets specified (use -h for help)\n"

The "return 1" isn't skipped as it was pretented? That would be a bit odd.

here its PKGBUILD pkgname=bsc-beta pkgver=4.0.05 pkgrel=1 pkgdesc="Two panels file mamager" arch=('i686' 'x86_64') url="http://www.beesoft.org/bsc.html" license="GPL" depends=('qt4') source=(http://www.beesoft.org/download/bsc_${pkgver}.beta_src.tar.bz2) md5sums=() build() { cd $startdir/src/bsc /usr/bin/qmake make PREFIX=/opt/bsc make PREFIX=$startdir/pkg/opt/bsc install || return 1 } I thing its bad to hide a error by default,maybe its useful a options like options=(emptypkg)