Charles Wilson wrote:
>>> Hey, yeah -- that'll work. Where should generic-* go -- in one of
>>> the existing repositories under cygwin-apps (probably not), or should
>>> I create another? If I should create another, what should it be
>>> called? resources?
>>>
>>
>> Hmm. Lets be a bit more specific - why not call the module "packaging".
>> Then the generics can go in /templates or /samples or something like
>> that.
>
>
>
> sounds find to me.
>
> packaging/
> packaging/ChangeLog
> packaging/templates/
> packaging/templates/generic-build-script
> packaging/templates/generic-readme
Okay -- I've done this. But, I've run into a snag: the cygwin-apps
repository is not accessible via cvsweb. Can somebody apply this patch
to the file 'cvsweb.conf' in the 'cgi-bin' module of the 'sourceware'
repository? (I don't have write access to that module).
--Chuck
Index: cvsweb.conf
===================================================================
RCS file: /cvs/sourceware/cgi-bin/cvsweb.conf,v
retrieving revision 1.51
diff -u -r1.51 cvsweb.conf
--- cvsweb.conf 17 Sep 2001 22:55:40 -0000 1.51
+++ cvsweb.conf 25 Apr 2002 16:28:54 -0000
@@ -29,6 +29,7 @@
'c++-embedded' => '/cvs/c++-embedded',
'cgen' => '/cvs/src',
'cygwin' => '/cvs/cygwin',
+ 'cygwin-apps' => '/cvs/cygwin-apps',
'cygwin-xfree' => '/cvs/cygwin-xfree',
'docbook-tools' => '/cvs/docbook-tools',
'dominion' => '/cvs/dominion',
