VectorLinux

Cooking up the Treats => New Package Requests => Topic started by: easuter on March 18, 2007, 06:17:40 am

Title: Commiting to build packages
Post by: easuter on March 18, 2007, 06:17:40 am
I was wondering if it might be a good idea for packagers to commit to build a package once a request is made, so as to avoid multiple build attempts?
That way we can avoid stepping on each others toes.

Example:

http://www.vectorlinux.com/forum2/index.php?topic=2409.0
Title: Re: Commiting to build packages
Post by: uelsk8s on March 19, 2007, 09:58:13 am
IMO this Needs to be done.
In the past we had a VL-packagers spreadsheet that had all the package names and their packagers name.
This helped us keep our small team from duplicating efforts.
I can make an online spreadsheet at numsum and I will even try to keep it as up to date as possible If this way is considered the best.

here is an example of what can be done: http://numsum.com/spreadsheet/show/41236

Uelsk8s
Title: Re: Commiting to build packages
Post by: Fragadelic on March 19, 2007, 10:14:51 am
Why not just create a wiki that the devs could update themselves.  Maybe this is what the "numsum" already is but in case it isn't, just a suggestion.

Title: Re: Commiting to build packages
Post by: LLL on March 19, 2007, 04:21:25 pm
We did try the package maintainer list previously.

Reasons for failure:
1) Only one person knew how it worked, and only two had editing access.
2) The first person (above) had to depart for personal reasons leaving only me (the incompetent-boob/database-newbie) to maintain the list.

My suggestions:
1) A publicly accessible/editable maintainers list.
2) Make it (signing up and adding your package info) part of the "How to be a packager" post to distribute the workload.
Title: Re: Commiting to build packages
Post by: JohnB316 on March 20, 2007, 09:53:30 am
I've got that sheet from the person who had previously maintained it. I'll merge what was there with the sample uelsk8s posted, then we can go from there.

Cheers,
John
Title: Re: Commiting to build packages
Post by: LLL on March 21, 2007, 05:47:31 pm
Great. I still have access to the original database if that helps - just not skilled enough to maintain it.

Let me know if I can be of help.

LLL
Title: Re: Commiting to build packages
Post by: caitlyn on June 11, 2007, 07:26:55 pm
My only concern is that while most packages are easy to build there a some others have proved to be problematic.  I posted about things I was building -- some showed up next day.  Others, like dia, continue to give me, um... interesting issues.  I put them aside for a while and then try again until I get it right.  If I had to work on package x to a deadline I'd only take packages I was comfortable with.  Right now it's still a learning experience and I don't mind tackling something with unusual issues.

Just my .02...

Cait
Title: Re: Commiting to build packages
Post by: Joe1962 on June 12, 2007, 06:09:32 pm
As long as this thread has been revived, I might as well post my commitment to keep packaging Gambas and Postgresql in spite of my current lack of time issues... Other stuff will be on a "maybe" basis... :(
Title: Re: Commiting to build packages
Post by: indubitableness on January 26, 2009, 04:32:08 am
  If we're committing to packages I am willing to commit to dosbox and zsnes right now. i built them by the old checkinstall standards so i need to redo them with sbbuilder. I'd have them up already but i've been doing homework all day.
Title: Re: Commiting to build packages
Post by: caitlyn on March 08, 2009, 04:43:22 pm
@indubitableness:  You're already listed as a packager.  Welcome aboard!  More volunteer packagers are always welcome.

If you already have access to the vectorcontrib area of the repo please be sure to upload the packages, source code, slack-desc file, and build scripts to a folder in your contrib directory.  If your packages have slack-required or slack-recommends files they need to be included as well. 

You should have been given access to the Packagers Board section of the forum.  If so please post there once you've uploaded.  If you have any questions about building a package they can also be posted in the Packagers Board.

Thanks again for packaging for Vector Linux.  It really is appreciated.

All the best,
Cait
repository maintainer
Title: Re: Commiting to build packages
Post by: no2thesame on April 29, 2009, 06:27:03 pm
  If we're committing to packages I am willing to commit to dosbox

indubitableness, did you ever package dosbox? I can't find it in the repos and will need it soon. If you don't have time, let us know and I'll attempt it.

Thanks
Title: Re: Commiting to build packages
Post by: Masta on January 24, 2010, 06:07:10 pm
Are there any packages left that I was building?
Title: Re: Commiting to build packages
Post by: retired1af on April 30, 2010, 08:03:41 am
I was going to try my hand at this today using the wonderfully detailed tutorial on opensourcebistro. But, the ones I see requests for are already done.

Was going to take a stab at Frostwire, but there's really no installation required with that. Untar it and it works.

So.............. Is there something out there that's not too stressful and folks need? LOL
Title: Re: Commiting to build packages
Post by: stretchedthin on April 30, 2010, 09:21:23 am
There is a newer wine package available.  It can be built with sbbuilder as a type=normal (the default) package.
Title: Re: Commiting to build packages
Post by: retired1af on May 01, 2010, 04:56:59 am
There we go! I'll get to it this weekend.  ;D
Title: Re: Commiting to build packages
Post by: retired1af on May 02, 2010, 05:06:14 pm
That wasn't too bad.  ;D

Got the latest wine (1.1.39) built and tested. What now?
Title: Re: Commiting to build packages
Post by: stretchedthin on May 02, 2010, 05:32:52 pm
Good stuff!!! I'll PM you with some additional instructions.