On Wed, Aug 02, 2000 at 07:47:09PM +0200, Andreas J. Koenig wrote:
> > The AUTHOR field is not related to the signature. Actually I would always
> > consider LArry as the author of perl, so I would expectLarry to appear
> > as the AUTHOR in the OSD, unless he said he want
and the
>> >> record can be edited by the person. PAUSE could refuse an upload if
>> >> the ID in the OSD isn't the same as the person doing the upload or
>> >> some such.
>>
>> > Would you always want to force that. For example why would the pe
ducers and consumers, otherwise
*>it will do what you say. Did I not make it clear enough that I want
*>security as an optional feature? The OSD should help to implement the
*>framework that allows security. Currently the options we have are all
*>too complicated. Please correct me if I&#
"Andreas J. Koenig" wrote:
> Did I not make it clear enough that I want security as an optional feature? The OSD
>should
> help to implement the framework that allows security. Currently the options we have
>are all
> too complicated. Please correct me if I&#x
Perl
> developers.
It must be an option item for both producers and consumers, otherwise
it will do what you say. Did I not make it clear enough that I want
security as an optional feature? The OSD should help to implement the
framework that allows security. Currently the options we have are all
too complicated. Please correct me if I'm wrong.
--
andreas
user knows that what they got is exactly what was uploaded.
> >> But
> >> they are in the PPD. Hmmm. I'd say, it should go away. The CPAN ID is
> >> fine, it is associated with a record in a public database and the
> >> record can be edited by the person. P
Elaine -HFB- Ashton wrote:
> Jeremy Wadsack [[EMAIL PROTECTED]] quoth:
> *>
> *>> A signature by PAUSE is an interesting idea. But it would tell the
> *>> user something different than a signature by a person. While I imagine
> *>> that a sig by GBARR would mean something like: "I have written
Jeremy Wadsack [[EMAIL PROTECTED]] quoth:
*>
*>> A signature by PAUSE is an interesting idea. But it would tell the
*>> user something different than a signature by a person. While I imagine
*>> that a sig by GBARR would mean something like: "I have written or at
*>> least doublechecked the code i
"Andreas J. Koenig" wrote:
> I had the imagination that the author would store a policy on PAUSE
> for uploads into his directory, and that the user would store a
> per-author policy for handling downloaded files from CPAN.
>
> If the author would decide in favor of policy "strict", PAUSE would
like to see besides author, email, name, version,
>> > url, signature, dependancies???
>>
>> I'd like to NOT have author's name and email in there because that is
>> redundant information and tends to get out of date.
> So does the README. It may b
> On Wed, 2 Aug 2000 10:04:53 +0100, Graham Barr <[EMAIL PROTECTED]> said:
> list of version numbers ? Do you mean the versions of all included modules ?
Yes. And version numbers of included scripts also come to mind.
--
andreas
> I'd like to NOT have author's name and email in there because that is
> redundant information and tends to get out of date.
So does the README. It may be redundant due to the fact that it is in an authors
directory on CPAN. But once the distribution leaves CPAN that knowledge is
l
On Tue, Aug 01, 2000 at 02:50:19PM -0500, Elaine -HFB- Ashton wrote:
> Andreas J. Koenig [[EMAIL PROTECTED]] quoth:
> *>- a signature
> *>- a list of namespaces used within the files that are being installed
> *> by this distribution
> *>- a list of version numbers
list of version numbers ? Do y
On Tue, Aug 01, 2000 at 04:59:42PM -0400, Chris Nandor wrote:
> At 14:50 -0500 2000.08.01, Elaine -HFB- Ashton wrote:
> >What else would people like to see besides author, email, name, version,
> >url, signature, dependancies???
>
> What about binary distributions?
At 04:59 PM 8/1/00 -0400, Chris Nandor wrote:
>At 14:50 -0500 2000.08.01, Elaine -HFB- Ashton wrote:
> >What else would people like to see besides author, email, name, version,
> >url, signature, dependancies???
>
>What about binary distributions?
And XS code optional? (I'd really like to be
at is
redundant information and tends to get out of date. We wouldn't want
to ask people to re-upload just because their email address has
changed, would we? Author's credentials are not in the OSD, right? But
they are in the PPD. Hmmm. I'd say, it should go away. The CPAN ID is
fine
At 14:50 -0500 2000.08.01, Elaine -HFB- Ashton wrote:
>What else would people like to see besides author, email, name, version,
>url, signature, dependancies???
What about binary distributions?
--
Chris Nandor | [EMAIL PROTECTED] | http://pudge.net/
Andover.Net| [
Andreas J. Koenig [[EMAIL PROTECTED]] quoth:
*>
*>I'm not arguing for changing the format but to optimize it for what we
*>are doing. The most urgent points I would like to see addressed are:
*>
*>- List of and checksums for all files in the distribution,
Could you elaborate on this a bit? What i
On 29 Jul 2000 10:19:36 +0200, Andreas J. Koenig wrote:
>>>>>> On Thu, 27 Jul 2000 13:13:59 +0100, Graham Barr <[EMAIL PROTECTED]> said:
> > One thing that came up during the meeting was that there should be
> > one OSD per dist which covers all implementat
Graham Barr [[EMAIL PROTECTED]] quoth:
*>> Ideally, we would change what 'make dist' is doing now without asking
*>> the user to do anything.
*>
*>Yes, I belive it should create the OSD file and include it, even though
*>it is not specified in the MANIFEST. Maybe i
d change what 'make dist' is doing now without asking
> the user to do anything.
Yes, I belive it should create the OSD file and include it, even though
it is not specified in the MANIFEST. Maybe it should add it to the MANIFEST
that is included if it is not specified in there already.
Graham.
>>>>> On Sun, 30 Jul 2000 19:47:57 +0100, Graham Barr <[EMAIL PROTECTED]> said:
>> > One thing that came up during the meeting was that there should be
>> > one OSD per dist which covers all implementatons. I was skeptical
>> > of this at the ti
ing about it I thought I'd post the URL for the OSD spec.
> >>
> >> http://www.w3.org/TR/NOTE-OSD
> >>
> >> While reading it two things were in question; how will it fit into the
> >> CPAN
>
> > This is TBD. But what I could see is an
>>>>> On Thu, 27 Jul 2000 13:13:59 +0100, Graham Barr <[EMAIL PROTECTED]> said:
> On Wed, Jul 26, 2000 at 12:35:39PM -0500, Elaine -HFB- Ashton wrote:
>> While I'm thinking about it I thought I'd post the URL for the OSD spec.
>>
>> http:
On Thu, Jul 27, 2000 at 12:46:13PM +0900, Simon Cozens wrote:
> On Wed, Jul 26, 2000 at 11:15:03PM +0300, Jarkko Hietaniemi wrote:
> > On Wed, Jul 26, 2000 at 12:35:39PM -0500, Elaine -HFB- Ashton wrote:
> > > While I'm thinking about it I thought I'd p
On Wed, Jul 26, 2000 at 12:35:39PM -0500, Elaine -HFB- Ashton wrote:
> While I'm thinking about it I thought I'd post the URL for the OSD spec.
>
> http://www.w3.org/TR/NOTE-OSD
>
> While reading it two things were in question; how will it fit into the
> CPAN
This
[Eric: This is from a list discussing how to add classification to the
Comprehensive Perl Archive Network]
On Thu, Jul 27, 2000 at 01:28:26AM -0400, Adam Turoff wrote:
> On Thu, Jul 27, 2000 at 12:46:13PM +0900, Simon Cozens wrote:
> > > People looking at OSD should probably also
On Thu, Jul 27, 2000 at 12:46:13PM +0900, Simon Cozens wrote:
> On Wed, Jul 26, 2000 at 11:15:03PM +0300, Jarkko Hietaniemi wrote:
> > People looking at OSD should probably also look at what metadata other
> > packaging systems (rpm, deb, pkgadd, ...) define and use.
>
> Wh
On Wed, Jul 26, 2000 at 11:15:03PM +0300, Jarkko Hietaniemi wrote:
> On Wed, Jul 26, 2000 at 12:35:39PM -0500, Elaine -HFB- Ashton wrote:
> > While I'm thinking about it I thought I'd post the URL for the OSD spec.
> >
> > http://www.w3.org/TR/NOTE-OSD
> >
On Wed, Jul 26, 2000 at 12:35:39PM -0500, Elaine -HFB- Ashton wrote:
> While I'm thinking about it I thought I'd post the URL for the OSD spec.
>
> http://www.w3.org/TR/NOTE-OSD
>
> While reading it two things were in question; how will it fit into the
> CPAN and h
While I'm thinking about it I thought I'd post the URL for the OSD spec.
http://www.w3.org/TR/NOTE-OSD
While reading it two things were in question; how will it fit into the
CPAN and how do we get people not only to use it but use it consistently.
It's food for thought anyway.
31 matches
Mail list logo
