Bug 2045

Summary:	Begin to regularly retire variables
Product:	[Build System, Metadata & Runtime] Meta-yocto	Reporter:	Dave Stewart <david.c.stewart>
Component:	meta-yocto	Assignee:	Alexandru Georgescu <alexandru.c.georgescu>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	alexandru.c.georgescu, bluelightning, laurentiu.serban, poky.bs.watcher, poky.watcher, sgw
Version:	unspecified
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Dave Stewart 2012-03-01 21:23:18 UTC

We should add a task to review all variables which really have been superceded and add a mechanism in bitbake to throw an error message if they are used, warning that their use will be eliminated in the next major rev of the Yocto Project. Then  every subsequent release needs to have this task added to add more to the list.

Comment 1 Richard Purdie 2012-03-01 21:48:37 UTC

Which variables have you in mind with regard to this? We don't retire variables that often...

Comment 2 Richard Purdie 2012-03-08 19:12:13 UTC

Need more info from Dave

Comment 3 Alexandru Georgescu 2012-08-27 09:13:52 UTC

Hi Dave,
Do you have any updates regarding this?

Comment 4 Dave Stewart 2012-08-27 18:57:03 UTC

At the time I submitted this bug, I was told (I'm pretty sure by Richard) that there were variables which used to be supported in Poky, but which are not in common use any more because their function has been replaced with newer variables. When we keep the old variables / tasks around that we don't test and are not in common use, it's an extra load on documentation. Also there is a risk that someone reads about them in the documentation, tries to use them and things blow up.  I want to minimize the stuff which hasn't been tested.

I suggest you go through the Yocto Project Reference Manual and review the lilst of variables and tasks. If there are some you find there which you don't think you have seen used, then flag them and have a 1-1 with Richard or Paul and see if we can safely put them on the path to removal.

I don't have specific examples in mind.

Comment 5 Laurentiu Serban 2012-09-12 20:54:45 UTC

I will take this for the moment.

Comment 6 Laurentiu Serban 2012-11-27 21:03:52 UTC

This will be implemented as test cases for each variable. There will be an automation testing suite covering this

Comment 7 Paul Eggleton 2017-06-08 06:28:18 UTC

I think over the last few releases we have demonstrated we're pretty good at cleaning out old variables that nobody is using. Given the non-specific nature of this bug I'm going to mark it resolved and if we have specific things we want to eliminate, we can open bugs for them (or just do the work as we have been).