Re: `cvs-buildpackage': Ideas and features
Hi,
>>"Karl" == Karl M Hegbloom <karlheg@bittersweet.inetarena.com> writes:
>>>>> "srivasta" == srivasta <srivasta@debian.org> writes:
Karl> Any way to parse the output of `tar t', and autogen a shell
Karl> script that creates the symlinks? You could then `cvs add'
Karl> that, and commit it right away, so it becomes part of every
Karl> branch.
There is a more genral CVS solution already. Also, I do not
thnk that in this case adding a script to the upstream sources is
justified. The CVS modules based solution works, is elegant, and has
been the way that CVS users would expect it to work. Also, parsing
the tar output is icky. find . -type l -print is a far better method,
if I were ever inclined to do it.
srivasta> * Both cvs-inject and cvs-upgrade warn about the presence of
srivasta> CVS directories in upstream source. This cannot be handled,
srivasta> and the operation aborts gracefully, and informs the user fo
srivasta> the offending directories.
Karl> Why can't you just use `cvs import ! CVS ...'?
Because that is beyond the scope of the script. The user can
set up whatever ignores they wish. In this case, let the human
decide.
Besides, CVS is alread an ignored file, so ignoring it does
not help. As I said, upstream CVS directories are an upstream bug,
and one that can not be handled by CVS, and hence cvs-buildpackage
and friends.
manoj
--
"It's no sweat, Henry. Russ made it back to Bugtown before he died.
So he'll regenerate in a couple of days. It's just awful sloppy of
him to get killed in the first place. Humph!" Ron Post, Post
Brothers Comics
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: