From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH] remove Default-Enabled from LSB header Date: Fri, 23 Jul 2010 20:39:25 +0200 Message-ID: <20100723183925.GC7603@aepfle.de> References: <20100723121917.GE3540@aepfle.de> <19529.51415.973935.754110@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <19529.51415.973935.754110@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Jul 23, Ian Jackson wrote: > Olaf Hering writes ("[Xen-devel] [PATCH] remove Default-Enabled from LSB header"): > > Default-Enabled: is not a LSB keyword. > > Move it out of the LSB section to avoid an openSuSE buildcheck warning. > > I'm pretty sure it was put there for a reason by the people who added > these files. If we move it out of the INIT INFO section it's probably > going to stop working. Its not clear what the intention was, LSB does not mention this keyword. Google has some hits about X-UnitedLinux-Default-Enabled: which implies what someone tried to get rid of the vendor part from this old string from end of 2002. I'm sure nothing will break if the lines disappear. > Is it actually a breach of the LSB spec to include nonstandard > keywords ? I havent checked if LSB forbids it. Most likely the tools should tolerate unknown keywords. Olaf