gnewsense-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnewsense-dev] README.gNewSense (was: [bug #38001] Kernel metapackages


From: Sam Geeraerts
Subject: [Gnewsense-dev] README.gNewSense (was: [bug #38001] Kernel metapackages (linux-latest-2.6) refer to missing Debian kernel versions)
Date: Fri, 4 Jan 2013 22:00:55 +0100

Op Fri, 04 Jan 2013 17:15:33 +1100
schreef Karl Goetz <address@hidden>:

> On Fri,   4 Jan 2013, 07:15:26 LHST, Sam Geeraerts
> <address@hidden> wrote:
> 
> Indeed, i will make a note to look at them though depending on how
> different they are it may be best to merge them gradually.

Ack.

> Pretty sure mine are a mix of rest and plain text too (if any of them
> survive :)).

True, judging by psutils. I thought you wrote something for linux-2.6
too, but I must have lost or overlooked that, because its current
readme is a lot more terse.

> > Sometimes someone comes along and asks what the difference between
> > Debian and gNewSense is. We should have a wiki page that lists our
> > changes. I was thinking we could use README.gNewSense files to
> > generate
> 
> interesting thought, i am wondering if pulling the info out of the
> wili at source package build time would be a better way to do it.

You're right, that avoids having to either manually update the page
using a browser or fiddling around with XML-RPC.

> > that automatically if we use a structured format (e.g. control file
> 
> or perhaps the machine readable copyright format to ease moving text
> between those files.

That's pretty much the same form with different keywords. Do you mean
to use keywords from copyright in README.gNewSense? What kind of text
would we want to move?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]