yes, pcbsd needs support, but...

[Amigamerlin]

Then what will be the point of having both self contained pbi, and "pkg_add" pbi ? :?

The point is to have a quickly and clean way to have installed as PBI package that can be too much difficult to realize as real PBI.

The good thing it that you can install it double klicking the package and have it as standard Pc-BSD with the icons, on the desk and the programs in the programs menu and you can uninstall it just like the other programs.

By the way I'm not inventing the wheel. I'm not the first that used pkg_add e pkg_delete in a PBI. If you take a look at the first linux compatibility layer build by kris you will see that he used the pkg_add and pkg_delete feature.
Go to figure to install linux abi layer as PBI can be really a pain in the ass.

The current K9copy require a lot of other bin to works properly and a lot of customization. In all my tentative adding missing bin and dll the package become about 20Mb and continue to not works because bin or dll is not linked or copied in the right place or because lack of other bin and dll that are really difficult to spot reading the error message poped out from Kde.

Using Pkg_add command the PBI was about 3mb and the software worked like a charm at the first try,

That's it . I'll write to kris about. Maybe we can have a official recognized PC-BSD SpecialPBI (SPBI) built in that way that can be usefull to be used when a software become too difficult to be realized like a standard PBI.

Bye.

[TerryP]

If your going to have a PBI that uses pkg_add/pkg_remove or w/e.

CREAT A FRONT END TO PACKAGES NOT ABUSE THE PBI CONCEPT PLEASE.

The PBI system is not supposed to effect the rest of the system. Like say, I removed GTK+ from my system. I could still use TheGimp PBI as it is self contained. - If I installed a "TheGIMP Pkg_Add PBI" it would have to install GTK+ and other packages to my system that I might not want if I for some reason removed them.

Now I know no ones going to be living in a Modren *Nix GUI w/o GTK stuff, but you see my point.
___

The PBI system is made to be that way ^ To be self contained and away from the rest of the system. Want to remove a PBI? run the wiz or rm -rf the programs directory.

If I install a PBI and then I look and see some funky pkg I never saw before in an audit I'd be checking where it came from in the logs and e-mailing the PBI maintainer a very naughty msg. For fooking with my system.

[mal.exe]

rm -rf the programs directory

This is exactly how a pbi (in my opinion) should be delete. If we're going to use pkg_add/delete, then we should drop the initial pbi idea.

[pcbsdusr]

I agree with mal if pbi's are to be fully self-contained.

I'd prefer pbi's to be able to share some components though for space and memory usage's sake. (Just one of my crazy ideas though )

[Amigamerlin]

mal.exe, Terryp, don't get me wrong but, I think, you all are loosing the point...

The point is not to change the goal of PBi, the point is to have as PBI some program that are really difficult to be realized as PBI.
I really don't want to change the idea of the PBI system, this is not in my intention.

As I wrote, in PC-BSD I can choose to install programs from ports and from package. This way to manage software is not wrongly and can be used too as primary management software in PC-BSD too.

IMHO the PBI has the goal to permit to install / remove the software in a simple way and to self cointan the programs. In that way you don't need to fight with dipendences.

If you look PBI system that way is not heretic talking of using pkg_add and pkg_delete. The PBI continue to self cointain the software (the goal is respected) and no need to fight dipendences too (goal continue to be respected).

Moreover we don't have to forgot that pkg_add and pkg_delete is the MAIN PRIMARY SOFTWARE MANAGEMENT SYSTEM OF FREEBSD where PC-BSD is based on and we don't have to forgot that to build a PBI we have first to install the software from ports or from package then you are going to manage software in the same way of a PBI that cointain pkg_add and pkg_delete!!!

I continue to don't see nothing of wrongly using Pkg_add inside PBI. Anyway I've wrote to kris highlighting him this topic. I really would like to know what he think about.

Anyway thanks you all guys for the patience and for letting me argue about this argument

Bye

[kmoore134]

I have occasionally used pkg_add / pkg_delete in a PBI, but only in some very RARE circumstances. For example, if I have a pkg file that doesn't require any dependancies, and can safely be added / removed without touching anything else on the system. However, these are few and far inbetween, most require several other packages.

When we run across a program that is difficult to convert to a self-contained PBI usually there is an answer somewhere. We should work to find out what the problem is, and then solve it, putting the info online for others to see I can take a peak at this k9copy program to see what I can do with it if you like .

[KLU]

Originally Posted by adonis

ok ok i was a little rough...i see...whole project is in the begining now. yesterday at night i installed PCBSD (tried 1.0 before) and it could't fetch freeBSD ports. it came to 22 % and stopped...ah...

Try installing PC-BSD 1.1

Actually I installed 1.1 and had this same issue (stalled at 22%) when I tried populating my ports tree via the tool in Computer > PC-BSD > System.
No prob when I used the console cvsup whatever the rest is...

[Amigamerlin]

Originally Posted by Amigamerlin

Originally Posted by adonis ok ok i was a little rough...i see...whole project is in the begining now. yesterday at night i installed PCBSD (tried 1.0 before) and it could't fetch freeBSD ports. it came to 22 % and stopped...ah... Try installing PC-BSD 1.1

Actually I installed 1.1 and had this same issue (stalled at 22%) when I tried populating my ports tree via the tool in Computer > PC-BSD > System.
No prob when I used the console cvsup whatever the rest is...

I've just intalled PC-BSD as a new VM and the upgrade was successuffly done in about 2 hour.

[Amigamerlin]

I have occasionally used pkg_add / pkg_delete in a PBI, but only in some very RARE circumstances. For example, if I have a pkg file that doesn't require any dependancies, and can safely be added / removed without touching anything else on the system. However, these are few and far inbetween, most require several other packages.

When we run across a program that is difficult to convert to a self-contained PBI usually there is an answer somewhere. We should work to find out what the problem is, and then solve it, putting the info online for others to see I can take a peak at this k9copy program to see what I can do with it if you like .

Thanks Kris.
Try to build a K9copy and let me know.
for me it started but was not fully working (lack of some other bin and libs that was inside dvd+rw-tools - dvdauthor-0.6.11 - cdrtools
etc. etc.).

I tried to fix it adding the missing bin but seems that some libs where not linked and placed in the right path.
At the end I've received a kde message system about an error and I was not able to fix it ( I continue to be a noob and just learning right now).

I'll study your PBI when ready.

Bye

PS. try to give a shoot at my k9pbi and let me know if it can be dungerous for the system.
The last one that I uploaded don't have the force option then the package will be installed if not already present and will be removed if not used by other apps.
Let me know if I've done something wrongly.

Bye

[TerryP]

Am I a fruit loop?

Ports have always been the primary method of package managment for my boxes.

I suppose I could see it in the case of what Kris pointed out. But for something, like say KOffice. pkg_add/pkg_delete would get my temper burning at the PBI maker :twisted: