NEW: py-xattr

[arsptr@…]

Note: This port uses the new subversion fetch code.

Seems to work OK for me, but I'm not sure how to declare a dependency on darwin >= 8.0... ?

[arsptr@…]

Portfile

[arsptr@…]

Portfile

[mww@…]

variants that change version (which the "current" variant does implicitely) are not allowed;

[arsptr@…]

(In reply to comment #3)

variants that change version (which the "current" variant does implicitely) are not allowed;

Apparently they are:

$ grep version editors/emacs/Portfile version 21.4a [...]

version 22.0.50 version 22.0.50.1

[arsptr@…]

Portfile

[yeled@…]

You could change the variant name to `devel' (something of a standard now) and use an svn.date argument perhaps.

[mww@…]

(In reply to comment #4)

(In reply to comment #3)

variants that change version (which the "current" variant does implicitely) are not allowed;

Apparently they are:

$ grep version editors/emacs/Portfile version 21.4a [...]

version 22.0.50 version 22.0.50.1

thanks, I've just fixed the emacs port!

[mww@…]

(In reply to comment #6)

You could change the variant name to `devel' (something of a standard now) and use an svn.date argument perhaps.

rather create a 2nd port thats named $name-devel

[yeled@…]

(In reply to comment #8)

(In reply to comment #6)

You could change the variant name to `devel' (something of a standard now) and use an svn.date argument perhaps.

rather create a 2nd port thats named $name-devel

agreed.

[arsptr@…]

(In reply to comment #8)

(In reply to comment #6)

You could change the variant name to `devel' (something of a standard now) and use an svn.date argument perhaps.

rather create a 2nd port thats named $name-devel

Will do that in future. For now it looks like bob has tagged a 0.2 release, so I've updated the portfile to use that.

[arsptr@…]

Portfile

[mww@…]

-I think we should label this Portfile as v1.2? (when did fetch.type/svn appear first?) is there perhaps a tarball available? (comes in _much_ more handy as we may mirror it, ppl. don't need subversion to build etc.) -create a variant like: platform darwin 7 {

fetch {

ui_msg "needs EA that are only available on darwin 8 and later!"

system "/bin/false" }

} thats should do the job (no guarantees on spelling errors)

[arsptr@…]

(In reply to comment #12)

-I think we should label this Portfile as v1.2? (when did fetch.type/svn appear first?) is there perhaps

a

tarball available? (comes in _much_ more handy as we may mirror it, ppl. don't need subversion to

build

etc.)

Agree, but unfortunately there is no tarball. This is from the MacPython project, and they have their own package management infrastructure, FWIW.

I will update to indicate Portfile 1.2

BTW maybe it is possible to simulate svn (of http urls) using recursive HTTP get (eg using libcurl) for those users who don't have svn installed? This should be sufficient for building anyway... ?

-create a variant like: platform darwin 7 {

fetch {

ui_msg "needs EA that are only available on darwin 8 and later!"

system "/bin/false" }

}

Sounds good, will do.

BTW it is claimed that this module works on modern linux also but I haven't tested this.

[arsptr@…]

(In reply to comment #13)

I will update to indicate Portfile 1.2

No I won't, because it breaks.

Suggest that if someone commits a change to implement Portfile 1.2, this port be updated, otherwise not.

svn fetching is new, committed 21-sep-05 if I'm not mistaken.

[arsptr@…]

Portfile

[mww@…]

I'll commit it as soon as 1.2 is released - remind me if not done immediately...

[arsptr@…]

(In reply to comment #16)

I'll commit it as soon as 1.2 is released - remind me if not done immediately...

Consider this a reminder :)

[mww@…]

thanks for the reminder - commited! :)