.pbi already bzipped

[Charles]

I think downloading packages in .tar.gz is misleading for newbies. Instead, I suggest the pbi be already compacted, like .exe for Windows.

[Anika]

I understand pc-bsd 's goal is to be a kind of geekproof bsd.
so my first thought was yes, that would be a good idea and one (little) step closer in achieving that goal...
on the other hand: it really isn't that hard. ;-)
and I think it's better to put everyone's precious time in one of the other zillion things that are much more important to become an easy to use desktop bsd.

:arrow: so I voted no

[Dingens]

i voted "yes" because it´s in line of the vision of pcbsd. but i think that this is a thing we can do later.

[youlle]

PBI's are already compressed, my first WINE.PBI turned a folder that was 600MB+ into a 120MB *.PBI

I think that's a good idea. But I don't think it's such a big deal right. The focus should be on desktop functionality first.

[Charles]

It's easy to switch now. I think if we switch, the earlier the better.
I'm pretty sure, most newbies have never heard of .tar.gz and wouldn't know how to handle it...

[youlle]

as i said PBI's are already compressed by the package creator.

[Charles]

as i said PBI's are already compressed by the package creator.

Then, why gzipping them for download ? :roll:

[youlle]

to make them smaller than they already are.

[mezziah]

to make them smaller than they already are.

Won't they get bigger like zip files do? I personally dislike the additional repackaging for the pbi's.

[Charles]

Me too, it's like zipping a .rar
It only complicates for newbies, and the rest of us :roll:

[kmoore134]

PBI's are already compressed before hand, But i'm also taking the additional precaution of gzipping them, since if you look at a "raw" PBI file, its got a shell-script wrapper on it. Taking this raw PBI file to a windows box, and burning it, or downloading improperly, may render it unusual, since the shell-script gets converted to the windows format.

I'm still looking into solutions to fix this :)

[JPortal]

I think that whatever is done, you should make installation files act more like Windows/Mac. For example, if you keep the current structure, you could just rename the files to "*.install" (the .install extension would also make it simpler for people). Then if someone double-clicks the .install file, it will unzip to /tmp or wherever and run the installer.
Whatever you do, people should just be able to double-click installer files and go. Just my $0.02.

Josh

[dixy]

PBI's are already compressed before hand, But i'm also taking the additional precaution of gzipping them, since if you look at a "raw" PBI file, its got a shell-script wrapper on it. Taking this raw PBI file to a windows box, and burning it, or downloading improperly, may render it unusual, since the shell-script gets converted to the windows format.

I'm still looking into solutions to fix this :)

Why not gzipping the whole file (including scripts) and making the install program read the scripts directly from the archive? Zlib library should help. I am offering myself to make such modifications.

[youlle]

a PBI is infact a SH script in its basic form which calls the various PC-BSD userland apps that make PC-BSD... PC-BSD. so you cant make the installer read the PBI when the PBI hasnt told it what to read.

[dixy]

a PBI is infact a SH script in its basic form which calls the various PC-BSD userland apps that make PC-BSD... PC-BSD. so you cant make the installer read the PBI when the PBI hasnt told it what to read.

More precise?

If we take a tar archive of app, add the scripts and gzip or bzip it, should be ok.