> A less magic approach would be checking for a file
> debian/dpep-debianonly or debian/patches/dpep-debianonly, which could
> optionally contain instructions on how to find the origtargz.
This sounds best to me, for the following reasons:
- One has to explicitly mark the tree as debian-only, so it can't be
misdetected (unless one deliberately breaks the thing)
- The file containing instructions can be a good idea.. I'm not 100%
sure about that though. (more on this later)
- It's VCS-agnostic
The only concern I have is the file to flag debian-only status. It might
be more useful if it would be debian/patches/00dpep-options (or
something similar), where one could tweak a selected set of
dpatch-edit-patch options. Not instructions on how to find the
orig.tar.gz though - that's a job of the origtargz finder script, and
debian/watch should be good enough for that. If not, then I think that
whoever is building the package should know how to get ahold of the
tarball and place it in a place where it can be found. That is, if
there's an easy way to automatically fetch the tarball, we should use
that. If there is not, we should rely on the user setting it up for us,
instead of performing BlackMagic(tm).
So, for now, I'd suggest a patch that checks
debian/patches/00dpep-options, and wether it sets a variable called
DEBIANONLY, and makes dpep act accordingly. And does nothing more.
(I'd imagine the function would look something like:
dpep_load_options ()
{
DEBIANONLY=""
if [ -e debian/patches/00dpep-options ]; then
. debian/patches/00dpep-options
fi
if [ ! -z "${DEBIANONLY}" ]; then
DPEP_DEBIANONLY="${DEBIANONLY}"
fi
}
(Thus, it does not allow setting all dpep options, only a selected set)
--
Gergely Nagy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
