On 24 May 2012 23:10, Ron <[email protected]> wrote: > Hi Brian, Hello Ron,
Thanks for your very prompt response. > Is there anything other than DEB_DIR that you can see your script likely > wanting to override to do what it needs to do? I guess my use case would be along the lines of scripting: TMPDIR=... DEB_DIR="$TMPDIR" gitpkg "debian/$VERSION" "upstream/$UPSTREAM" cd "$TMPDIR/$SOURCE/$SOURCE-$UPSTREAM" This is still a bit non-optimal in that I don't know the $SOURCE value that gitpkg worked out. Not sure what the best solution is here, ideally I would need the value of "$DEB_DIR/$DEB_SOURCE/$DEB_PACKAGE" after gitpkg exits. Am going to have to think about this a bit more. Maybe a hook could be used to write the environment variables to a file, that then could be parsed/sourced caller. Except the hook can't be specified on the command line. Also, if the user has set gitpkg.exit-hook to "/usr/share/gitpkg/hooks/dpkg-buildpackage-exit-hook" as per documentation this might mess my script up. Suddenly gitpkg does a lot more then expected. Not something I need to worry about personally, for the more general case might be an issue. Thanks -- Brian May <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
