Elder Scrolls Online AddOns » Utilities » Developer Utilities » Package
  • Addon Info.
  • Change Log
  • Other Files (3)
  • Comments (5)
    • Download
    (740 b)
    Download
    Updated: 11/14/15 04:43 PM
    Compatibility:
    Orsinium (2.2.4)
    Update 7 (1.7.0)
    Update 6 (1.6.5)
    Updated:11/14/15 04:43 PM
    Created:09/03/15 08:49 PM
    Monthly downloads:125
    Total downloads:6,519
    Favorites:0
    MD5:
    Package  Popular! (More than 5000 hits)
    Version: 1.3
    by: haggen [More]
    Packages your add-on ready for distribution.

    Check this out:

    ★ Archive all files described in your manifest, keeping the same folder structure you created.
    ★ Automagically names the package with the add-on name and version. e.g. Addon-1.0.zip
    ★ Parse special syntax like $(language) in your manifest, copying the correct files.

    How to use?

    1. Move the script package.bat within your add-on folder.
    2. Run it. The package will appear in the same folder.

    That's it. Done. Just go upload your add-on already!

    Optionally you can provide a package.manifest to list all files you'd like to include in the package but are not in the add-on manifest, like readmes, notes, licenses, etc.

    You can get it here or check the source at GitHub.

    Please note that it requires 7-Zip to work. You can get it free!

    Please report any bugs and provide feedback at the comment section above. Thank you!
    Sat, 14 Nov 2015 22:36:23 GMT

    - Renamed package.txt to package.manifest to avoid ESO detecting it as an add-on

    Fri, 04 Sep 2015 9:31:31 GMT

    - Prompt for add-on name when the folder name doesn't match the manifest file.
    - Use .package temporary folder name so to avoid collision.

    Fri, 04 Sep 2015 7:08:50 GMT

    - Reads from package.txt to include files not described in the manifest.
    - Parse $(language) as * so to copy any language file.
    Optional Files (0)


    Archived Files (3)
    File Name
    Version
    Size
    Uploader
    Date
     Package
    1.2
    731B
    haggen
    09/04/15 09:28 AM
     Package
    1.1
    697B
    haggen
    09/04/15 07:20 AM
     Package
    1.0
    705B
    09/03/15 08:49 PM


    Post A Reply Comment Options
    Unread 05/25/19, 07:53 AM  
    manavortex
     
    manavortex's Avatar
    AddOn Author - Click to view AddOns

    Forum posts: 138
    File comments: 511
    Uploads: 46
    Hey haggen,
    I tweaked a bit:
    https://gist.github.com/manavortex/68f3bfe57937346f68a40024532a0c29

    Works for me, maybe you want to check it out.
    Last edited by manavortex : 05/25/19 at 11:23 AM.
    Report comment to moderator  
    Reply With Quote
    Unread 09/04/15, 07:47 AM  
    haggen
     
    haggen's Avatar
    AddOn Author - Click to view AddOns

    Forum posts: 137
    File comments: 104
    Uploads: 10
    Originally Posted by merlight
    Originally Posted by haggen
    There's one problem though with using *, if the manifest has something like:

    Code:
    $(language).lua
    Then it becomes *.lua. That's not exactly bad but not right either. It might contain a lua file that's not in the manifest, that we don't want to load.
    Hm, true. Does path expansion in windows support character classes already? [a-z][a-z].lua would match en.lua, de.lua, ru.lua, everything that's two ascii lowercase letters dot lua. Or make it ??.lua that worked in DOS IIRC
    I was actually looking for that! Hahah I'll update if and when I found something. Thanks!

    BTW, I updated it with a 'packge.txt' where you include files like README, LICENSE, etc.
    Report comment to moderator  
    Reply With Quote
    Unread 09/04/15, 07:40 AM  
    merlight
    AddOn Author - Click to view AddOns

    Forum posts: 671
    File comments: 213
    Uploads: 12
    Originally Posted by haggen
    There's one problem though with using *, if the manifest has something like:

    Code:
    $(language).lua
    Then it becomes *.lua. That's not exactly bad but not right either. It might contain a lua file that's not in the manifest, that we don't want to load.
    Hm, true. Does path expansion in windows support character classes already? [a-z][a-z].lua would match en.lua, de.lua, ru.lua, everything that's two ascii lowercase letters dot lua. Or make it ??.lua that worked in DOS IIRC
    Last edited by merlight : 09/04/15 at 07:42 AM.
    Report comment to moderator  
    Reply With Quote
    Unread 09/04/15, 06:49 AM  
    haggen
     
    haggen's Avatar
    AddOn Author - Click to view AddOns

    Forum posts: 137
    File comments: 104
    Uploads: 10
    Originally Posted by merlight
    Looks useful, at least for people not using git archive I'm using a similar script written in bash. Few suggestions:

    - add some means of including files not in the manifest, e.g, README, (UN)LICENSE
    - language extensions should not be hardcoded
    if the manifest contains l10n/lang_$(language).lua, you should copy l10n/lang_*.lua
    Hm that's some good points thanks!

    There's one problem though with using *, if the manifest has something like:

    Code:
    $(language).lua
    Then it becomes *.lua. That's not exactly bad but not right either. It might contain a lua file that's not in the manifest, that we don't want to load.
    Last edited by haggen : 09/04/15 at 07:03 AM.
    Report comment to moderator  
    Reply With Quote
    Unread 09/04/15, 03:39 AM  
    merlight
    AddOn Author - Click to view AddOns

    Forum posts: 671
    File comments: 213
    Uploads: 12
    Looks useful, at least for people not using git archive I'm using a similar script written in bash. Few suggestions:

    - add some means of including files not in the manifest, e.g, README, (UN)LICENSE
    - language extensions should not be hardcoded
    if the manifest contains l10n/lang_$(language).lua, you should copy l10n/lang_*.lua
    Report comment to moderator  
    Reply With Quote
    Post A Reply


    Report this file Report this File

    Category Jump: