oapp-developers@lists.launchpad.net
Subject: Re: [Coapp-developers] CoApp and
I'd just stick with a LICENCE file in the package, and use a parser like
Debian's build system does (matches common licences)
This just sounds like complication for complication's sake.
In
I'd just stick with a LICENCE file in the package, and use a parser
like Debian's build system does (matches common licences)
This just sounds like complication for complication's sake.
Interesting idea though.
--Adam
___
Mailing list: https://launchp
Fredrik,
Just skimming through this and looking at some of the sample files, I see
the use of something along these lines. One issue I see though is that the
standard seems incredibly verbose. Every file in a package must be
checksummed and must have it's own license defined. Also since our packag
day, October 29, 2010 8:42 AM
To: coapp-developers@lists.launchpad.net
Subject: Re: [Coapp-developers] CoApp and Windows Error Reporting/crashdump
collection...
Howdy!
The certificate is actually $99, if you click through to Verisign via WinQual.
(Or click the link below.)
https://securitycenter.ve
Howdy!
The certificate is actually $99, if you click through to Verisign
via WinQual. (Or click the link below.)
https://securitycenter.verisign.com/celp/enroll/upsell?promo_code=THEDEAL99&application_locale=VRSN_US&originator=VeriSign:CELP&bundle_id=MSIECS002&enable_option
On Fri, Oct 29, 2010 at 2:01 PM, Jonathan Wilson wrote:
> Are there any plans for CoApp to feature crashdump collection? Will it be
> handled by going through Windows Error Reporting/WinQual? (if so how will it
> be handled for all those who cant afford the $500 price tag of the VeriSign
> certifi
6 matches
Mail list logo
