Sublime Forum

Package Control settings "bootstrapped"

#1

Hi,

I’d like to know whats the “bootstrapped”: true is for. I use to maintain and distribute my settings via git to the different computers i’m working with and I’d like to know if I can commit this line.

Thanks

Silberling

2 Likes
#2

It tracks whether the binary _ssl dependencies have been bootstrapped by Package Control already so that it can submit installation records for itself or should do it on the next restart. This was part of a bugfix in 3.1.

0 Likes
#3

This setting should not be present if you are copying settings to a new machine. I suppose I may need to add some more logic to ensure that if it is copied, it doesn’t result in anything blowing up.

0 Likes
#4

… like instead of having a boolean value use a timestamp and compare with the bootstrapped data?

Thank you so far for the information. SourceTree makes it pretty easy to skip this line, I just wanted to know.

0 Likes
#5

@wbond: I’ve been skipping the “bootstrapped” line in SourceTree, just like @Silberling suggested, but I’m leaning towards committing it since both my computers always seem to have it set to true. Have you added logic so nothing blows up in Package Control?

More generally, why do we have temporary/cache fields in “Package Control.sublime_settings”? I’m referring particularly to “bootstrapped” and “in_process_packages”. Couldn’t they live inside another file in “Package Control.cache/” which can easily be ignored when transferring settings using git or equivalent?

0 Likes
#6

Hey @fgb,

AFAIK you COULD commit this line but you SHOULDN’T. One problem that might happen is, when you have a fresh installation of Sublime and check out your config, Packages like Mediawiker, … which might rely on SSL connections might not work properly.

As @FichteFoll and @wbond said, this flag is to indicate that SSL dependencies have been processed successfully. So this line will always come back and will be a simple boolean true after the SSL setup has been done successfully.

I still use git and skip this line. As of today I have some more files and lines which I have to skip every and I just don’t care anymore. It’s not a big deal to be careful when committing new settings and I’d rather spend more time on getting things done :slight_smile:

EDIT: Just have seen the date of your post…

0 Likes
#7

ST should ship all required dependencies by PC by now (_ssl and bz2), so that setting value is ineffective for those builds.

0 Likes
#8

@Silberling I understand. I’m still skipping the line. I just wish there were no temporary/cache fields mingled with Package Control settings.

@FichteFoll Does this mean that the “bootstrapped” line will go away sometime soon?

1 Like
#9

Maybe. Maybe not. It is still required for older builds, although technically a different mechanic could be used to store the bootstrapping state. Either way, it certainly won’t “hurt” committing it now, but I do realize this is not what you are after.

0 Likes
#10

The project is open source! Make some suggestions, discuss, then implement![quote=“fgb, post:8, topic:15732”]
Does this mean that the “bootstrapped” line will go away sometime soon?
[/quote]

Probably not until support for older builds is dropped. https://github.com/wbond/packagecontrol.io/issues/90 has some stats. Currently about 15% of users still need to be bootstrapped in some fashion.

1 Like
#11

@wbond Fair point. Now that you’ve joined the Sublime Text team, should we expect Package Control to keep its independence or will it be folded into ST?

0 Likes
#12

At the current time our plans are to keep Package Control separate from the Sublime Text codebase, although Sublime Text does now come with a built-in command that will install Package Control.

0 Likes