[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Port policies.

Ok, so you mean not all port maintainers have a CVS account to update the tree,
I didn't know that. So everytime a port is updated it will depend on another
maintainer to take the diff file and apply it to the port, then it will become
updated and available for system update by CVS.

Thanks Andreas.

On 10/3/05, Andreas Kahari <andreas_(_dot_)_kahari_(_at_)_gmail_(_dot_)_com> wrote:
> Hi João,
> I'm a port maintainer, which means I look after a few smaller
> applications (stow, anacron, mcl etc.)  I have no CVS commit rights,
> so when I want to update one of my ports I send a text diff to the
> ports mailing list, hoping someone here will take it, test it, and
> commit it (I obviously do as much testing as possible myself first).
> Once it is commited and the CVS mirrors have picked it up, anyone
> checking the ports tree out can use it.
> This is described here:
> http://openbsd.org/checklist.html
> http://openbsd.org/porting.html
> http://openbsd.org/ports.html
> Andreas
> On 03/10/05, João Salvatti <salvatti_(_at_)_gmail_(_dot_)_com> wrote:
> > Hi all,
> >
> > I'd like you to explain me something. When a maintainer decides to
> > create a new port or when he decides to update an existing port, does
> > this port become already available from CVS? For example: A maintainer
> > creates a new port. an HTML editor, so if he wants to make it
> > available from the port tree, the only necessary thing would be to
> > update the port under CVS? Is it the same thing to have a port
> > updated? Could please anyone explain me how this happens, or just tell
> > me where I could find informations about it?
> --
> Andreas Kahari

João Salvatti
Undergraduating in Computer Science
Federal University of Para - UFPA
web: http://salvatti.expert.com.br
e-mail: salvatti_(_at_)_gmail_(_dot_)_com