Re: pkgsrc question

["Jeremy C. Reed" <reed@xxxxxxxxxxxxx>]

On Thu, 22 Mar 2007, Kevin L. Kane wrote:

> Based on what i've been reading i should be able to create a binary
> package of something after its installed, however if i do 'bmake
> package' after i already did 'bmake install' it fails with errors, and
> the only way to fix this is to 'pkg_delete <package>' and then do
> 'bmake package'(which not only creates the binary package but installs
> as well and will fail to create the binary package if it cannot
> install).  Is this normal, the documentation I look at for netbsd
> seems to suggest that i can cd into a package dir, then do this:
> 
> bmake
> bmake install
> bmake package

That should work fine.

Do you happen to have some mk.conf option to do a "clean" also?
  
Was your work directory gone before you did the "bmake package"? I guess 
not since your lines below jump to "Installing".

I can not reproduce this on DragonFly. It works for me as expected. 
For example, a "bmake install" ends with:

. ..
=> Registering installation for screen-4.0.3
=> Checking for missing run-time search paths in screen-4.0.3
=> Checking for work-directory references in screen-4.0.3
=> Checking file-check results for screen-4.0.3
=> Checking file permissions in screen-4.0.3
WARNING: [check-perms.mk] Skipping file permissions check.
WARNING: [check-perms.mk] Install sysutils/checkperms to enable this 
check.


Do you have the following file?

pkgbox:/home/reed/pkgsrc/misc/screen> cat work.reed/.install_done 
screen-4.0.3

Next step works for me:

pkgbox:/home/reed/pkgsrc/misc/screen> bmake package
=> Required installed package digest>=20010302: digest-20060826 found
===> Checking for vulnerabilities in screen-4.0.3
=> Checksum SHA1 OK for screen-4.0.3.tar.gz
=> Checksum RMD160 OK for screen-4.0.3.tar.gz
===> Building binary package for screen-4.0.3
Creating package /home/reed/packages/All/screen-4.0.3.tgz
Using SrcDir value of /home/reed/pkg




  Jeremy C. Reed