I just up graded to Features 6.x-1.0-beta10. When I recreate my features with beta10, the file that gets downloaded is a .tar (not a .tgz, which is what previous versions of Features created).

This doesn't really bother me. But I assume the intention is to have Features compress (zip) the tarballs.

For people who don't know, if your feature is a .tar file, you can unpack it like this: 

$ tar xvf example-6.x-1.0.tar

Comments

yhahn’s picture

yhahn commented
Status: Active » Closed (works as designed)

It turns out this is by design and I forgot to note it in the beta9 release notes.

In @dmitrig01's reimplementation of the feature packaging to include other (non-features) files in a module, using just tar lets us stream the archive as its generated making it less likely that PHP will run out of memory as it serves the feature.

Will make note of it in the next release.

jayson’s picture

jayson commented

Hi,

I've just gone through the exercise of getting a feature server setup and got stuck on compression formats; it seems to me that if you run your own feature server, that you need to attach a .tgz file as .tar files are incompatible with drush -dl and such. It's a lot of manual trouble to get a .tar, uncompress it, re-compress it to the .tgz format, and then upload it to your feature server each time you make a change to your feature.

If my understanding is correct here, I would request that the features module provide the option to download a .tgz as well as a .tar. What do you think? Or is there a better/quicker way for me to get a .tgz version of my features after I modify/create them?

Tks, Jayson

jayson’s picture

jayson commented

Sorry, I do know this issue is closed and just found this issue that is exactly what I'm requesting, so I +1'd it: http://drupal.org/node/912976#comment-4600422.