Achim Gratz <strom...@nexgo.de> writes:
> Jambunathan K writes:
>> Mainline version
>>
>> 1. Doesn't update `archive-contents' which is necessary in order to
>> browse packages in the repo with `list-packages'. My private version
>> does it with `package-upload-file'.
>
> That's the right place to do it, so that'll be implemented with the
> upload.
>
>> 2. Doesn't create README file.
>
> Can't do either, since the source for the new README isn't included in
> Git. I do package the README, though.
>
>> 3. Packs the whole repo. My private version packs just the "original"
>> org-odt.el and style files.
>
> Wait, are we talking about the same ELPA Org package? I don't pack the
> whole repo either, just lisp/, etc/styles, doc and a few files from
> toplevel.
If I am not mistaken, you are talking about release tar and not the ELPA
tar. They are not the same.
Run rgrep like so.
(rgrep "pkg" "*.mk" "~/src/org-mode/" nil)
and I see no references to 'org-pkg.el'. (Note the `-pkg.el')
Look at following info node in Emacs-24+
(info "(elisp) Multi-file Packages")
specifically this paragraph:
,----
| For example, if we distribute version 1.3 of the superfrobnicator
| as a multi-file package, the tar file would be
| `superfrobnicator-1.3.tar'. Its contents would extract into the
| directory `superfrobnicator-1.3', and one of these would be the file
| `superfrobnicator-pkg.el'.
`----
You can also look at
http://elpa.gnu.org/packages/
to understand how things are packaged.
>
>
> Regards,
> Achim.
--
