headers
Bill Fenner | 1 Sep 16:08
Picon

Re: assigning bugs

I have some modified scripts that allow submission of followups (not new
bugs) via email.  It's mostly already present in the bugzilla contrib/
directory.  I suspect something to do reminders is there too, but as
Daniel said, it'd be fairly trivial to do with database access.  I've
even been doing a lot of scripts that submit forms and parse the resulting
HTML recently, but I'd rather avoid that if at all possible.

I've used rt a little, and like it, but I think that switching from
bugzilla to RT would be a small incremental improvement for a large
amount of pain.

  Bill
Permalink | Reply | 0 comments |
headers
Sterling Garwood | 1 Sep 18:22
Picon

How to get started?

I am trying to get Portsmanager.app as documented at 
http://www.opendarwin.org/projects/darwinports/en/
but it doesn't seem to be there ... so how do I get started ... or has 
the world moved on to another method?
Permalink | Reply | 0 comments |
headers
Felix Kronlage | 2 Sep 16:36

unmaintained ports

These is a list of ports, that are currently maintained by
'darwinports <at> opendarwin.org' and thus, look for a real maintainer :)

audio/audiofile
comms/dgpsip
comms/scud
databases/gtksql
databases/mysql
devel/gettext
devel/ruby-cocoa
graphics/gimp
graphics/imlib
graphics/jpeg
graphics/lcms/
graphics/libungif
irc/infobot
mail/ssmtp
textproc/chef
www/lynx
x11/XFree86/

If one is interested in taking over a port, please submit a patch with the
change of maintainer (and possibly update to most recent, stable version)
into bugzilla.

felix
--

-- 
  gpg-fingerprint: 076E 1E87 3E05 1C7F B1A0  8A48 0D31 9BD3 D9AC 74D0 
| Felix Kronlage                    | http://www.hazardous.org/fkr/    |
| fkr@{grummel.net|opendarwin.org}  | http://www.opendarwin.org/~fkr/  |
(Continue reading)

Permalink | Reply | 2 comments |
headers
Felix Kronlage | 2 Sep 17:06

Re: DP receipts schema

On Mon, Aug 25, 2003 at 09:15:46PM -0700, Kevin Van Vechten wrote:

> Landon and I use the (name, epoch, version, revision) tuple to uniquely 
> identify a port.  name and version are the intuitive values.  revision 
> is any change to the portfile for the same version of a port (starts at 
> zero for a new version).  

We finally need to clarify when to increment revision. eric@ told me
(back when I started with DP) that revision should only be incremented
if the resulting install/the binary significantly changes *without* a changed
version. "any change to the portfile" is something completly different,
and we should try to become consistent with that.
I'd go with 'any change to the Portfile' since that seems the most intuative.

felix,
(heh, somehow I overlooked what you wrote about revision last time I read
that mail and just stumbled across it, summing up the "big disussion")
--

-- 
  gpg-fingerprint: 076E 1E87 3E05 1C7F B1A0  8A48 0D31 9BD3 D9AC 74D0 
| Felix Kronlage                    | http://www.hazardous.org/fkr/    |
| fkr@{grummel.net|opendarwin.org}  | http://www.opendarwin.org/~fkr/  |
Permalink | Reply | 6 comments |
headers
Jim Mock | 2 Sep 18:36

Re: unmaintained ports

On Sep 2, 2003, at 7:36 AM, Felix Kronlage wrote:
> These is a list of ports, that are currently maintained by
> 'darwinports <at> opendarwin.org' and thus, look for a real maintainer :)

[snip...]

> databases/mysql
> devel/gettext

I'm going to hate myself for doing this, but I suppose I'll take both 
of these since I've been dealing with mysql a lot lately and gettext is 
needed by the gtk/gtk2 stuff.

I'll change the Portfiles later this afternoon.

- jim

--

-- 
jim mock <mij@{soupnazi|opendarwin}.org>       work: jim <at> streamzap.com
http://soupnazi.org             Streamzap, Inc. | http://streamzap.com
Permalink | Reply | 0 comments |
headers
Jim Mock | 2 Sep 18:38

Re: DP receipts schema

On Sep 2, 2003, at 8:06 AM, Felix Kronlage wrote:
> On Mon, Aug 25, 2003 at 09:15:46PM -0700, Kevin Van Vechten wrote:
>> Landon and I use the (name, epoch, version, revision) tuple to 
>> uniquely
>> identify a port.  name and version are the intuitive values.  revision
>> is any change to the portfile for the same version of a port (starts 
>> at
>> zero for a new version).
>
> We finally need to clarify when to increment revision. eric@ told me 
> (back when I started with DP) that revision should only be incremented 
> if the resulting install/the binary significantly changes *without* a 
> changed version. "any change to the portfile" is something completly 
> different, and we should try to become consistent with that.  I'd go 
> with 'any change to the Portfile' since that seems the most intuative.

I agree with Eric 100% on this one--it should only be bumped if ther 
eare significant changes made without a version bump.  There's no need 
whatsoever to bump the revision if you're, for example, fixing typos in 
the Portfile or something else that doesn't affect the installed port.  
It should only be done if there have been changes to what's installed.

- jim

--

-- 
jim mock <mij@{soupnazi|opendarwin}.org>       work: jim <at> streamzap.com
http://soupnazi.org             Streamzap, Inc. | http://streamzap.com
Permalink | Reply | 0 comments |
headers
Landon Fuller | 2 Sep 19:51
Picon
Favicon

Re: DP receipts schema

On Tuesday, Sep 2, 2003, at 08:06 US/Pacific, Felix Kronlage wrote:

> On Mon, Aug 25, 2003 at 09:15:46PM -0700, Kevin Van Vechten wrote:
>
>> Landon and I use the (name, epoch, version, revision) tuple to 
>> uniquely
>> identify a port.  name and version are the intuitive values.  revision
>> is any change to the portfile for the same version of a port (starts 
>> at
>> zero for a new version).
>
> We finally need to clarify when to increment revision. eric@ told me
> (back when I started with DP) that revision should only be incremented
> if the resulting install/the binary significantly changes *without* a 
> changed
> version. "any change to the portfile" is something completly different,
> and we should try to become consistent with that.
> I'd go with 'any change to the Portfile' since that seems the most 
> intuative.
>
> felix,
> (heh, somehow I overlooked what you wrote about revision last time I 
> read
> that mail and just stumbled across it, summing up the "big disussion")

Revision exists for the upgrade scenario (which doesn't exist, but was 
planned for). If the revision is incremented every time you change the 
portfile, every 'client' of that portfile must upgrade their copy of 
the port, regardless of the nature of your change. This is not 
acceptable for a one-line comment change or similar.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Felix Kronlage | 2 Sep 20:06

Re: DP receipts schema

On Tue, Sep 02, 2003 at 10:51:20AM -0700, Landon Fuller wrote:

> Revision exists for the upgrade scenario (which doesn't exist, but was 
> planned for). If the revision is incremented every time you change the 
> portfile, every 'client' of that portfile must upgrade their copy of 
> the port, regardless of the nature of your change. This is not 
> acceptable for a one-line comment change or similar.
> The revision should only be incremented when the resulting 
> package/installed files/etc significantly changes. If you fix a typo in 
> the documentation, that's no reason to upgrade every installed port. 
> The revision line should be removed (where it will default back to '0') 
> when you bump the epoch or the version.

thanks for the clarification. This should definitly make it into guide.

felix
--

-- 
  gpg-fingerprint: 076E 1E87 3E05 1C7F B1A0  8A48 0D31 9BD3 D9AC 74D0 
| Felix Kronlage                    | http://www.hazardous.org/fkr/    |
| fkr@{grummel.net|opendarwin.org}  | http://www.opendarwin.org/~fkr/  |
Permalink | Reply | 2 comments |
headers
Gregory Wright | 2 Sep 20:14
Picon

gprolog port

Dear Paulo,

I've updated your portfile for gprolog. It is in the bugzilla as an 
attachment
to bug 840.

You have to update your darwinports installation. The installation phase
is now split into two parts: installation into a temporary directory, 
which allows
an inventory of files to be made, followed by copying to the final 
destination.

gprolog does not properly support the staging directory, so I had to do 
a
number of fixes by hand. I also made the installation correspond to 
darwinports
conventions (i.e., put library files in 
${prefix}/lib/${name}-${version} instead of
${prefix}/${name}-${version}/lib.)

swi-prolog has a similar problem, but I haven't looked at it in detail.

Yap fails to build as well in the bugzilla attached Portfile. I'll look 
at it when
I get a chance.

Best Wishes,
Greg

Greg Wright, satrap of the /lang hierarchy.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Will Barton | 2 Sep 22:11

Re: [Doc] Re: DP receipts schema

Now that I have some time (again), I'll finish up my run through the 
Guide (updating the stuff I already updated, etc ;), I'll take care of 
this too! :)

-will

On Tuesday, September 2, 2003, at 08:06  PM, Felix Kronlage wrote:

> On Tue, Sep 02, 2003 at 10:51:20AM -0700, Landon Fuller wrote:
>
>> Revision exists for the upgrade scenario (which doesn't exist, but was
>> planned for). If the revision is incremented every time you change the
>> portfile, every 'client' of that portfile must upgrade their copy of
>> the port, regardless of the nature of your change. This is not
>> acceptable for a one-line comment change or similar.
>> The revision should only be incremented when the resulting
>> package/installed files/etc significantly changes. If you fix a typo 
>> in
>> the documentation, that's no reason to upgrade every installed port.
>> The revision line should be removed (where it will default back to 
>> '0')
>> when you bump the epoch or the version.
>
> thanks for the clarification. This should definitly make it into guide.
>
> felix
> -- 
>   gpg-fingerprint: 076E 1E87 3E05 1C7F B1A0  8A48 0D31 9BD3 D9AC 74D0
> | Felix Kronlage                    | http://www.hazardous.org/fkr/    
> |
(Continue reading)

Permalink | Reply | 1 comment |

Gmane