On Tue, 4 May 2004, Daniel Reed wrote:
On 2004-05-04T09:33-0400, Igor Pechtchanski wrote:
) On Mon, 3 May 2004, Daniel Reed wrote:
) Creating an initial ticket:
) Go to http://example.com/package-maint/, fill out form with information
) and email address. ALTERNATIVELY: Send new-style
Dan,
I didn't have the time to review this in detail, but one suggestion is
below...
On Mon, 3 May 2004, Daniel Reed wrote:
[snip]
This is what I would like to implement:
Creating an initial ticket:
Go to http://example.com/package-maint/, fill out form with information
and email
Anyway, is this crackrock? Good stuff? Suggest any tweaks?
This looks great.
It would be good if the site could subscribe to the cygwin-apps mailing list
and parse replies to the initial announcement so they also got included on
the website.
Chris
On 2004-05-04T09:33-0400, Igor Pechtchanski wrote:
) On Mon, 3 May 2004, Daniel Reed wrote:
) Creating an initial ticket:
) Go to http://example.com/package-maint/, fill out form with information
) and email address. ALTERNATIVELY: Send new-style setup.hint to
) [EMAIL PROTECTED].
) Also,
On 2004-05-04T16:25+0100, Chris January wrote:
) It would be good if the site could subscribe to the cygwin-apps mailing list
) and parse replies to the initial announcement so they also got included on
) the website.
I've been trying to get something like that working during weekends more or
On 2004-03-27T00:26-0500, Daniel Reed wrote:
) To propose a new package, one would simply send the proposed initial
) contents of the package's .hint file to the cygwin-apps mailing list. An
...
) I have not decided on an optimal machine-readable format for announcing
) updates. If the hint URL
On Mar 27 00:26, Daniel Reed wrote:
If no #!src is provided, external-source will be required in the final
.hint. If no external-source is provided when one is needed, the field will
be set to the first complete package preceeding the current one. That is,
in the above example, libfoo-devel
On 2004-03-29T11:57+0200, Corinna Vinschen wrote:
) On Mar 27 00:26, Daniel Reed wrote:
) If no #!src is provided, external-source will be required in the final
) .hint. If no external-source is provided when one is needed, the field will
) I would refuse the package instead. Otherwise we could
Currently, I store all package information in a large XML
document which I update by hand whenever a new package is
ITPd, an existing package is updated, or some other change
must be made against the live repository. XSL transformations
convert this XML document into several other formats,
On 2004-03-27T08:38-0500, Sergey Okhapkin wrote:
) package name=libfoo version=0.01 release=1
) sdesc The Finite Object Organization library/
Close :)
The existing data looks like:
app
nameaspell-de/name
related-toaspell/related-to
maintainerDr. Volker
On Sat, Mar 27, 2004 at 02:17:45PM -0500, Daniel Reed wrote:
Currently, only my tools use the XML format. All of the utilities that deal
with setup.ini, including the most important utility--setup.exe itself--only
use the structured-text format found in current setup.hint files. The
proposal was
On Sat, Mar 27, 2004 at 12:26:41AM -0500, Daniel Reed wrote:
4) Perform automated sanity checks against the bin package.
5) Push the new hint, bin, and src packages into the live repository.
I think these two features, especially the sanity checks, make it
worth the small changes. Of
12 matches
Mail list logo
