Adopt an orphaned port project

conta

New Member

Reaction score: 5
Messages: 15

I get error:

Code:
# nawk -F"|" '$6 == "ports@FreeBSD.org" {print $2}' /usr/ports/INDEX-`uname -r | cut -d'.' -f1`
nawk: can't open file /usr/ports/INDEX-11
 source line number 1
 

yuripv

Well-Known Member

Reaction score: 127
Messages: 285

I get error:

Code:
# nawk -F"|" '$6 == "ports@FreeBSD.org" {print $2}' /usr/ports/INDEX-`uname -r | cut -d'.' -f1`
nawk: can't open file /usr/ports/INDEX-11
source line number 1

Do a make fetchindex in /usr/ports.
 

nunotex

Member

Reaction score: 14
Messages: 61

rigoletto@

Daemon
Developer

Reaction score: 1,185
Messages: 2,219

IIRC that list is of very regular contributors, usually src contributors. I think they have some more access/privileges internally.
 
OP
lme@

lme@

Administrator
Staff member
Administrator
Moderator
Developer

Reaction score: 303
Messages: 776

IIRC that list is of very regular contributors, usually src contributors. I think they have some more access/privileges internally.
No, it's for all contributors. But there's nothing that adds a new contributor automatically. Someone has to add it manually. I'll add you, [USER=57794]nunotex[/USER]
 
OP
lme@

lme@

Administrator
Staff member
Administrator
Moderator
Developer

Reaction score: 303
Messages: 776

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 9,504
Messages: 34,294

Add yourself as MAINTAINER in the Makefile.
I'm seriously considering taking up emulators/mame (and by extension emulators/mess) but are there any rules regarding the maintainer name? Do I need to use my real name or would "SirDice" be acceptable too? I haven't been able to find anything in this respect.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 9,504
Messages: 34,294

You just need a valid email address.
In my case they're both somewhat related. It's the choice between my own personal domain or my GMail account. I'm leaning towards GMail for this as the information is publicly visible and I'm probably going to get more spam as a result. I'm just going to let Google filter out most of that crap.

Expect a patch some time soon (within a few days) :D
 

userxbw

Well-Known Member

Reaction score: 32
Messages: 424

1. Some of these I use have not and do not really need to be updated they are so old yet still work. ie dockapps for wmaker. so there really is no need to purge them from the system on the grounds that no one is the maintainer of same said app.
 

chrcol

Well-Known Member

Reaction score: 44
Messages: 449

Hi guys, what about ports that still have a maintainer listed, but have been orphaned?

Some high profile ports are been orphaned its scary.

pftop
ifstat
zfs-stats
mcrypt
mhash
and ruby-bdb

zfs-stats and pftop used for core freebsd features.
mcrypt and mhash depended on by lots of stuff.
ruby-bdb is needed by portupgrade a major ports maintainer tool.

When I ran the command to check for ports that have no maintainer, a lot of this list isn't there as they listed with a maintainer. There is also ports been removed because they not the latest version anymore some of them with claims of "unsupported by upstream" when that is not true. Would I be able to make new ports of old versions of software?

libunwind is another port, that is completely broken on clang 8.0 which is now the base compiler in FreeBSD, I fixed it locally to get it to compile (just had to update src tarball and distfiles file as the one in ports tree is 2 years old), but again it has a maintainer listed.
 

rigoletto@

Daemon
Developer

Reaction score: 1,185
Messages: 2,219

You have two different situations: orphaned ports are maintained by ports@ (aka the pool) which means we maintain them as possible. The other situation are the abandoned ports, those are the ports with a maintainer listed but who in practice don't maintain anything (and we don't get the notice when there is an update because that goes to the maintainer) .

In regards to the orphaned situation you can open a bug report with patch adding you as maintainer, and if the port need update/fixed they should also be done in the patch.

In case of an abandoned port basically the same except you should tell the port looks unmaintained, and the `maintainer` will be informed by e-mail to agree or not. If he/she don't tell anything in two weeks the port is yours (but this is not automatic/scripted), or if he/she say no and keep not maintaining the port, the port is also likely to be yours later. Sometimes there is some major blockers forbidding you to update the port.

Thank you.
 
Top