Re: Source package policy problem.
>>"Adam" == Adam McKenna <adam@debian.org> writes:
>> Uhh, why are there no redistribution terms on your package?
>> (and since you do not in any way, shape, or form include Dan's
>> code, your code is all that is in the package)
Adam> There aren't any. The problem is that the "source package"
Adam> that I use to build the installer package contains the original
Adam> source
Uhh, why?
Adam> (the .diff.gz needs to be included in the installer
Adam> package)..
Which diff.gz file is this?
Adam> That source package cannot be uploaded to debian
Adam> machines, or redistributed at all for that matter. So, I am in
So the source for your package can't be distributed at all?
Just because you dumped the original, undistributable source in there
with your installer package? Don't do that, then.
Adam> the (somewhat unique) position of having a package that has no
Adam> .orig.tar.gz.
That is not very unique. Every single debian specific package
is in the same boat.
Adam> Really, the only solution I can come up with is to make the
Adam> .dsc, .changes, and .diff file separately, and manually copy
Adam> them over to a second build dir where I make the installer
This is wrong, and a violation of policy in any case.
Adam> package. So, I was hoping for a more automated way of doing
Adam> this.
Oh, for heavens sake. Start a fresh directory, called
foo-installer. Create a ./debian directory. create a script that
called create-foo-pkg-now (or something you like better); Also create
./debis-dir-for-foo/debian.
You installer package shall then have this in the .deb:
/usr/bin/create-foo-pkg-now
/usr/share/man/man1/create-foo-pkg-now.1.gz
/usr/share/foo-installer/debian.tar,gz
/usr/share/doc/foo-installer/copyright et al
There is no orig.tar,gz, or a diff file, and by no means you
ship Dan's code with you package.
Now, the users can run the script /usr/bin/create-foo-pkg-now
when they wish, and what this script does is this:
======================================================================
Firstly, it creates a directory, say /tmp/foo-installer-$$ (iff the
dir does not exist, and bailing on error).
Next, it
a) downloads foo using wget or something, or
b) requires the pathname of the location that the admin has
downloaded sources into.
Next, it uncompresses the sources located in the previous step
Next, it chages directory into the unpacked source dir (dpkg-source
provides an example)
# cd foo-X.X.XX
Then,
# tar zvvfx /usr/share/foo/debian.tar.gz
which unpacks into ./debian
Then run dpkg-buildpackage -rfakeroot or something, and you are
done.
======================================================================
The user then installs ../foo_blah.deb
manoj
--
Date: 18 Apr 90 23:02:31 GMT From: merlyn@iwarp.intel.com (Randal
Schwartz) $_='vec(1,1,1); print substr($_ ^
"<\020\020\134\021M_CEA^RP\042\014\034\030\000\033\024\001\030\
021\000\004",0,25)'; eval
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: