Jesse Smith | 7 Jun 15:37 2010
Picon

PBI Module to test

Hello List,

Today I tried to make my first PBI module, based on the FreeBSD Ports
collection. I'm testing the waters with a small app, figure it'll be
easier that way.

Would someone here be willing to test my module to make sure I've done
this correctly? It seems to work okay on my machine, but I'm a complete
novice at this. (Module is attached.) The module should build a classic
arcade game called Sopwith, where the player flies around fighting
AI-controlled planes and shoots at buildings.

Any feedback is appreciated.

- Jesse

Attachment (sopwith-module.tar.gz): application/x-compressed-tar, 4374 bytes
_______________________________________________
Pbi-dev mailing list
Pbi-dev@...
http://lists.pcbsd.org/mailman/listinfo/pbi-dev
Kris Moore | 7 Jun 14:26 2010

Re: PBI Module to test

On 06/07/2010 13:37, Jesse Smith wrote:
> Hello List,
>
> Today I tried to make my first PBI module, based on the FreeBSD Ports
> collection. I'm testing the waters with a small app, figure it'll be
> easier that way.
>
> Would someone here be willing to test my module to make sure I've done
> this correctly? It seems to work okay on my machine, but I'm a complete
> novice at this. (Module is attached.) The module should build a classic
> arcade game called Sopwith, where the player flies around fighting
> AI-controlled planes and shoots at buildings.
>
> Any feedback is appreciated.
>
> - Jesse
>
>    

Tested the module out here. Seems to build / run just fine!

My comments would be thus:

Rename kmenu-dir/0mymenu -> kmenu-dir/sopwith

In kmenu-dir/sopwith, fix a few things:

Add an icon to ExeIcon: sopwith.png (Then put some sopwith.png into 
overlay-dir)

(Continue reading)

Jesse Smith | 7 Jun 22:15 2010
Picon

Re: Sopwith Module

Kris,

Thanks very much for your quick feedback. I made the changes you
suggested and I'm re-submitting the module here. (Please see attached.)

I do have a question about the build target. There's an option for
giving a specific version of PC-BSD to build against and I believe the
default is 7.2. Will that cause problems for people running more modern
versions of PC-BSD?

Jesse

-----Original Message-----
From: pbi-dev-request@...
Reply-to: pbi-dev@...
To: pbi-dev@...
Subject: Pbi-dev Digest, Vol 39, Issue 1
Date: Mon, 07 Jun 2010 12:00:01 -0700

Send Pbi-dev mailing list submissions to
	pbi-dev@...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.pcbsd.org/mailman/listinfo/pbi-dev
or, via email, send a message with subject or body 'help' to
	pbi-dev-request@...

You can reach the person managing the list at
	pbi-dev-owner@...

(Continue reading)

Kris Moore | 7 Jun 18:39 2010

Re: Sopwith Module

On 06/07/2010 20:15, Jesse Smith wrote:
> Kris,
>
> Thanks very much for your quick feedback. I made the changes you
> suggested and I'm re-submitting the module here. (Please see attached.)
>
> I do have a question about the build target. There's an option for
> giving a specific version of PC-BSD to build against and I believe the
> default is 7.2. Will that cause problems for people running more modern
> versions of PC-BSD?
>
> Jesse
>    

The build target version is something special, and rarely needs to be 
used. The only port we use it for is virtualbox, since it needs to 
compile its kernel module on 7.2 and later only.

In this case, you would leave it unset, and it'll compile on the default 
build environment (7.0, 8.0 & 9.0), which means users of later versions, 
I.E: 7.1, 8.1, 8.2, will still be able to run the same PBI file and have 
it work.

BTW, your new module looked just fine now. I've already committed it to 
subversion, and we should
see a new PBI get built for each platform in the next few days:

http://trac.pcbsd.org/changeset/6874

64bit Build Server:
(Continue reading)

Joachim Holzwarth | 9 Jun 23:39 2010
Picon
Picon

commit module audio/easytag

Hello,

I tried myself in creating PBIs, so here is my first working one. It's for 
Easytag, a tag-editor for audio files.  
I hope more modules will follow, as far as time permits.

Joachim

Attachment (easytag.tar.bz2): application/x-bzip-compressed-tar, 21 KiB
_______________________________________________
Pbi-dev mailing list
Pbi-dev@...
http://lists.pcbsd.org/mailman/listinfo/pbi-dev
Kris Moore | 10 Jun 19:35 2010

Re: commit module audio/easytag

On 06/09/2010 17:39, Joachim Holzwarth wrote:
> Hello,
>
> I tried myself in creating PBIs, so here is my first working one. It's for
> Easytag, a tag-editor for audio files.
> I hope more modules will follow, as far as time permits.
>
> Joachim
>
>    

Just did a build of the app here, compiles / runs great! I've committed 
it to our
server, and we should get a PBI built of it in the next few days or so:

http://trac.pcbsd.org/changeset/6892

Feel free to send any others in that you get done, we'll get them added 
as well.

Thanks!

BTW, in the overlay-dir/ folder, the PBI.UpdateURL.sh isn't needed, 
since its set by our build-server automatically.

--

-- 
Kris Moore
PC-BSD Software
iXsystems
(Continue reading)

Jesse Smith | 14 Jun 22:40 2010
Picon

Sopwith module

Sometime last week I submitted a pbi module for Sopwith. I believe the
module was placed in the build queue, but it hasn't shown up on
pbidir.com. When I checked the auto-build console it lists the build
status as "Failed". (http://pbibuild64.pcbsd.org/)

Does this mean there was something wrong with the module I submitted? I
notice a few packages are also showing failed build status and I'm
curious what might be causing that?

Thanks,
Jesse
Kris Moore | 15 Jun 17:04 2010

Re: Sopwith module

On 06/14/2010 16:40, Jesse Smith wrote:
> Sometime last week I submitted a pbi module for Sopwith. I believe the
> module was placed in the build queue, but it hasn't shown up on
> pbidir.com. When I checked the auto-build console it lists the build
> status as "Failed". (http://pbibuild64.pcbsd.org/)
>
> Does this mean there was something wrong with the module I submitted? I
> notice a few packages are also showing failed build status and I'm
> curious what might be causing that?
>
> Thanks,
> Jesse
>
>
>
> _______________________________________________
> Pbi-dev mailing list
> Pbi-dev@...
> http://lists.pcbsd.org/mailman/listinfo/pbi-dev
>    

Jesse,

It's still in the works :)

The module built just fine here:

http://pbibuild64.pcbsd.org/index.php?ver=8

A lot of ports got updated in the last few weeks, and the build server 
(Continue reading)

Jesse Smith | 19 Jun 00:21 2010
Picon

SETI at Home client

FreeBSD has a SETI at Home client in the form of the packages
boinc-client and boinc-gui. I've tried to combine these into one PBI
module. There's an option in the PBI config file that seems to be used
to importing files from other ports, but I'm not sure how it works.

Could someone here please take a look at my module and let me know
if/how to polish it up so both ports are included in the one package?

Thanks,
Jesse

Attachment (setiathome.tar.gz): application/x-compressed-tar, 25 KiB
_______________________________________________
Pbi-dev mailing list
Pbi-dev@...
http://lists.pcbsd.org/mailman/listinfo/pbi-dev
Joachim Holzwarth | 19 Jun 11:15 2010
Picon
Picon

Re: SETI at Home client

Hi Jesse,
I checked your pbi.conf. I think it's not necessary to set the OTHERPORTS 
option to boinc-client if you only want to create a SETI PBI, because the 
boinc-setiathome-enhanced port depends on boinc-client, so that port will be 
built automatically.
I tried to create a PBI for this BOINC stuff just about two weeks ago as well. 
Unfortunately it failed to build. My entry for the "PBIPORT" was the boinc-
client port and I set the "OTHERPORTS" option to boinc-milkyway, boinc-
setiathome-enhanced and boinc-simap, so the user had been able to choose 
between at least three projects to participate. I can't remember what 
prevented the PBI to build, so I can't give you any further hints... 
regards
Joachim

Am Samstag, 19. Juni 2010 00:21:34 schrieb Jesse Smith:
> FreeBSD has a SETI at Home client in the form of the packages
> boinc-client and boinc-gui. I've tried to combine these into one PBI
> module. There's an option in the PBI config file that seems to be used
> to importing files from other ports, but I'm not sure how it works.
> 
> Could someone here please take a look at my module and let me know
> if/how to polish it up so both ports are included in the one package?
> 
> Thanks,
> Jesse
> 

Gmane