buildroot/package/skeleton, branch 2016.08

system: do not set hostname and issue for custom skeleton

2016-07-18T21:45:49+00:00

We expect the custom skeleton to be fully filled with the necessary files, now. There is definitely no reason we should handle setting the hostname and the issue file in there. A user using a custom skeleton should be fully responsible for providing a functional skeleton. Signed-off-by: "Yann E. MORIN" Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

system: do not handle network settings for custom skeleton

2016-07-18T21:45:34+00:00

We expect the custom skeleton to be fully filled with the necessary files, now. There is definitely no reason we should handle network settings in there. A user using a custom skeleton should be fully responsible for providing a functional skeleton. Signed-off-by: "Yann E. MORIN" Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

system: provide no default for custom skeleton path

2016-07-18T21:40:06+00:00

Being custom means that our default one is not suitable to start with. So there is no reason to offer it as the default path. Add a check that it is not empty. Add a separating empty line, for good measure, too. Signed-off-by: "Yann E. MORIN" Cc: Romain Naour Cc: Arnout Vandecappelle Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

package/skeleton: respect variables namespace

2016-07-05T13:22:51+00:00

In makefiles, variables have global scope. We traditionally ensure that we get no name clashing by prefixing all variables with the package name. Currently, this is not the case in the skeleton package, for historical reasons (code snippets copied over from the common Makefiles). We currently have a mix of naming for the variables: - some are indeed prefixed with SKELETON_ - some are prefixed with SYSTEM_ - some are prefixed with both - some are not prefixed Clean up these discrepancies, and prefix all variables with just SKELETON_ and drop the SYSTEM_ prefix. Also include SET_ in all variables that do set something (getty) for consistency across all the variables. Signed-off-by: "Yann E. MORIN" Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

skeleton: remove SOURCE variable

2016-07-03T10:58:14+00:00

Now that the package infrastructure doesn't attempt to download a package that has an empty version string, there's no need to define the SOURCE variable in the skeleton package. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

package/skeleton: fix message about non-merged custom skeleton

2016-05-24T20:12:18+00:00

Use of a merged /usr is not restricted to systemd anymore, thus the current error message is misleading, as it only speaks about systemd. Fix the message by just ditching the reference to systemd altogether. Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

skeleton: move LIB_SYMLINK definition from Makefile

2016-01-20T20:49:14+00:00

Commit 7a6b83a211612ff95a1f5d35b2861ad5655ac8b1 introduced the skeleton package, which took over the lib32/lib64 -> lib symlink creation from the main Makefile. However, the definition of the LIB_SYMLINK variable did not move along, for no real reason. Signed-off-by: Thomas De Schampheleire Cc: Thomas Petazzoni Cc: Arnout Vandecappelle Signed-off-by: Thomas Petazzoni

skeleton: fix indentation of generated interfaces file

2016-01-11T16:30:53+00:00

The generated $(TARGET_DIR)/etc/network/interfaces mixes spaces and tabs. Fix by using tabs only. Signed-off-by: Luca Ceresoli Signed-off-by: Peter Korsgaard

skeleton: fix VCS folders not being excluded from rootfs

2015-12-31T09:35:13+00:00

There is a typo in skeleton.mk preventing rsync from excluding VCS folders such as .svn. Signed-off-by: Nathan Ford Signed-off-by: Thomas Petazzoni

Merge branch 'next'

2015-12-01T22:24:07+00:00

Signed-off-by: Peter Korsgaard