On Mon, Dec 09, 2002 at 09:50:22PM -0500, Joey Hess wrote:
> Denis Barbier wrote:
> > For translators having a development URL is also useful, because they can
> > then send up to date translations; it was said that it is then available
> > from package homepage, but some packages have no homepage
On Mon, Dec 09, 2002 at 06:27:55PM -0800, Osamu Aoki wrote:
> ...
> > +The single line synopsis
> >
> >
> > The single line synopsis should be kept brief - certainly
The line that follows is:
under 80 characters.
This is a sufficient restriction IMO.
--
On Sun, Dec 08, 2002 at 04:32:10PM -0600, Adam DiCarlo wrote:
>Is it a good practice for SGML or XML documentation to ship with
>source?
My preference would be to include the source plus both text and html
renderings. This provides both convieniently pre-formated output for
on-line viewing plus t
On Tue, Dec 10, 2002 at 11:23:41PM +1100, Brendan O'Dea wrote:
> >Is it a good practice for SGML or XML documentation to ship with
> >source?
>
> My preference would be to include the source plus both text and html
> renderings. This provides both convieniently pre-formated output for
> on-line v
Joey Hess <[EMAIL PROTECTED]> writes:
> Package: debian-policy
> Version: 3.5.8.0
> Severity: normal
>
> As discussed earlier on this list, and now implemented by lots of stuff
> in Debian[2] and with only a few to go[3], I'm proposing that the
> following be added to policy around section 12.4:
On Tue, Dec 10, 2002 at 12:34:17AM +0100, Denis Barbier wrote:
> On Mon, Dec 09, 2002 at 11:28:46PM +, Julian Gilbey wrote:
> [...]
> > I doubt that translators will need to extract such information in an
> > automatic manner.
>
> If these informations were available,
> http://www.debian.o
Josip Rodin <[EMAIL PROTECTED]> writes:
> On Mon, Dec 09, 2002 at 01:17:28PM -0600, Adam DiCarlo wrote:
> > > The point was validly raised in a previous thread that using these means
> > > changing packages twice in the event that dpkg is eventually changed.
> >
> > That I don't follow.
>
> Scen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 10 December 2002 10:57, Denis Barbier wrote:
[Initial request was to include author and/or homepage for package in the
control file and as a result in the Packages file (IIRC)]
> Please ignore my initial request, I no longer need extra fie
On Tue, Dec 10, 2002 at 09:03:54AM -0600, Adam DiCarlo wrote:
> As for the extra work, it doesn't matter.
It's not nice to screw around with other people's time like that.
--
2. That which causes joy or happiness.
Josip Rodin <[EMAIL PROTECTED]> writes:
> On Tue, Dec 10, 2002 at 09:03:54AM -0600, Adam DiCarlo wrote:
> > As for the extra work, it doesn't matter.
>
> It's not nice to screw around with other people's time like that.
I was under the guess that given the qty of dpkg bugs, it might take
6+ mont
On Tue, Dec 10, 2002 at 10:49:14AM -0600, Adam DiCarlo wrote:
> > > As for the extra work, it doesn't matter.
> >
> > It's not nice to screw around with other people's time like that.
>
> I was under the guess that given the qty of dpkg bugs, it might take
> 6+ months, so a best practice stop-gap
On Tue, Dec 10, 2002 at 04:49:38PM +0100, Josip Rodin wrote:
> On Tue, Dec 10, 2002 at 09:03:54AM -0600, Adam DiCarlo wrote:
> > As for the extra work, it doesn't matter.
> It's not nice to screw around with other people's time like that.
But no one is *required* to do anything. (Yet, if ever.)
On Sat, Dec 07, 2002 at 05:33:10PM -0500, Clint Adams wrote:
> > True. It could get away with tossing everything outside angulars or
> > inside brackets, though. The address can be mandated to stay 7bit for
> > now.
>
> At any rate, people shouldn't be putting raw Latin1 in these fields.
Amen. 7
[EMAIL PROTECTED] (Denis Barbier) writes:
> Putting it in a README file won't help, it can't be automatically
> extracted. The problem is that debian/control is the only file with
> a parsable format, maybe such infos could be added to another file,
> say debian/infos, in a standardized manner.
James R. Van Zandt wrote:
> I think the link in the copyright file to the upstream sources should
> be in a standardized, parsable format. Likewise the author name.
> That way lintian could check for them. The last time I checked, 5 or
> 10 percent of our packages lacked any link to the upstream
15 matches
Mail list logo
