On 3/28/06, Daniel Schepler <[EMAIL PROTECTED]> wrote:
> Le Mardi 28 Mars 2006 12:33, vous avez écrit:
> > Hello Daniel,
> >
> >
> > This is not a bug, but a feature ;)
>
> Well, let me explain in more detail why I was trying to build with a custom
> version number, and then let you decide: I've been working on a Perl script
> named pbuildd to rebuild the Debian archive from scratch. In order to
> support using the result as a source for installing packages locally, I need
> to differentiate the generated packages from the official packages somehow,
> or apt often will not know to install the local package over the package from
> the Debian archives. The best way to do this seemed to be to use something
> similar to the new binNMU versioning scheme, which shouldn't cause problems
> with most packages.
>
> That said, I suppose I could add a blacklist for the script to consult -- but
> I'd rather not unless I absolutely had to, and then somebody building apt-zip
> locally might not actually be using the result. :) And I definitely don't
> want to start special-casing any more than necessary, so setting DEV=yes just
> for that package is out of the question.
Is there any special environment variable set during a bin NMU?
Instead of DEV we could use that.
Another option would be to have a more relaxed check for the version,
something like
test "$$DEV" = "yes" -o "${DVERSION}" = `echo "${UVERSION}" | sed
s/\(.*\)\+.*/\1/`
instead of the current:
test "$$DEV" = "yes" -o "${DVERSION}" = "${UVERSION}"
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
