build make_portable() functions

[jafeha]

we've decided to extract all the applications to to tempdir and to split the further process of making the applications portable. each application or extension gets an own make_portable() function to focus on the special needs of every application.

some applications only need to be copied to another directory, others need have to be more complicated. for installing the extensions for example, we have to determine the ID of each extension before we can move them to their destination.

so far, i'd say we nee:

• make_portable_tblinux()
• make_portable_tbwin()
• make_portable_tbmac()
• make_portable_vidalialinux()
• make_portable_vidalialwin()
• make_portable_vidaliamac()
• make_portable_torbirdy()
• make_portable_enigmail()
• make_portable_gpg4usb()
• make_portable_gpg4mac()
• make_portable_gpg4tb()

i'd suggest to move this logic to make_portable.py and the extract logic back to extract_files.py. it's getting a bit messy in utils.py.

[jojoo-]

maybe we should approach this in bunches: first tblinux and the xpi's needed for that. only tblinux.

when we have tblinux running, we know a lot more about thunderbird, xpi, makeing things protable, so that we can approach other stuff

[jafeha]

yep. i thought pretty much the same today. in the end, we will need all of those functions above, or at least most of them. it's possible, that we won't need gpg4tb under linux, because gpg4usb supports both linux and windows. but we will need all the other functions, if they just move stuff from the tempdir to their destination or if they need more sophisticated routines.

[jojoo-]

i'd say we have to tidy up the last bit of parabird_build.p, but then we can actually close this issue

[jafeha]

closed.