Fix trailing line for package.el compatibility #1

Merged
merged 1 commit into from Mar 28, 2013

Conversation

Projects
None yet
2 participants
@purcell
Contributor

purcell commented Mar 28, 2013

The trailing line requires 3 leading semicolons in order to be parsed by package-buffer-info. Without this fix, the file cannot be installed from the automatically-built packages on MELPA.

Fix trailing line for package.el compatibility
The trailing line requires 3 leading semicolons in order
to be parsed by `package-buffer-info`. Without this fix,
the file cannot be installed from the automatically-built
packages on MELPA.

sabof added a commit that referenced this pull request Mar 28, 2013

Merge pull request #1 from purcell/patch-1
Fix trailing line for package.el compatibility

@sabof sabof merged commit e92c6a3 into sabof:master Mar 28, 2013

@sabof

This comment has been minimized.

Show comment Hide comment
@sabof

sabof Mar 28, 2013

Owner

Thanks, I have probably have done the same in other packages. Will have a look.

Owner

sabof commented Mar 28, 2013

Thanks, I have probably have done the same in other packages. Will have a look.

@purcell

This comment has been minimized.

Show comment Hide comment
@purcell

purcell Mar 28, 2013

Contributor

Super, that would be really helpful. I've just changed MELPA so that uninstallable packages will not be listed, so I'm going through the list of failing packages and submitting fixes where possible. :-)

Contributor

purcell commented Mar 28, 2013

Super, that would be really helpful. I've just changed MELPA so that uninstallable packages will not be listed, so I'm going through the list of failing packages and submitting fixes where possible. :-)

@sabof

This comment has been minimized.

Show comment Hide comment
@sabof

sabof Mar 28, 2013

Owner

Not exactly sure what are you cooking. I assume this needs to be done client-side. If it's server-side, it might be easier to "upgrade" package-buffer-info

Owner

sabof commented Mar 28, 2013

Not exactly sure what are you cooking. I assume this needs to be done client-side. If it's server-side, it might be easier to "upgrade" package-buffer-info

@purcell

This comment has been minimized.

Show comment Hide comment
@purcell

purcell Mar 28, 2013

Contributor

I'm just trying to make sure all single-file packages pass the standard package-buffer-info checks.

Contributor

purcell commented Mar 28, 2013

I'm just trying to make sure all single-file packages pass the standard package-buffer-info checks.

@sabof

This comment has been minimized.

Show comment Hide comment
@sabof

sabof Mar 28, 2013

Owner

Done

Owner

sabof commented Mar 28, 2013

Done

@purcell

This comment has been minimized.

Show comment Hide comment
@purcell

purcell Mar 28, 2013

Contributor

Cool, thanks.

Contributor

purcell commented Mar 28, 2013

Cool, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment