--On October 2, 2012 11:28:12 PM +0200 Michael Gmelin <free...@grem.de>
wrote:
On Tue, 02 Oct 2012 14:14:26 -0500
Paul Schmehl <pschmehl_li...@tx.rr.com> wrote:
--On October 2, 2012 2:44:46 PM -0400 Eitan Adler
<li...@eitanadler.com> wrote:
> On 2 October 2012 14:37, Paul Schmehl <pschmehl_li...@tx.rr.com>
> wrote:
>> I obviously wasn't very clear. I'm a port maintainer. I need to
>> update one of my ports. I used to do this by checking out the
>> port into a purpose-created directory in which I would use cvs to
>> make changes and test. After everything checked out, I would
>> submit the diff.
>
> We need to be better about announcing these changes as not to
> frustrate maintainers. :)
>
>> Now cvs isn't working, so how, as a port maintainer, do I check
>> out a single port so I can update it and submit it in a PR?
>
> You should do things the same way you did before, but instead you
> should use svn to checkout out your port. Note that 'module names'
> no longer work so you must use the full name:
> e..g., svn checkout svn://svn.freebsd.org/ports/head/editors/nano
>
> It may help to keep a folder of "ports-I-maintain" with the ports
> you maintain checked out. Before you update them do "svn update *"
> and to generate a diff do "svn diff foldername"
I got on the wiki and figured out how to check ou the port using svn,
but now I'm stuck again. This port has moved to github, and I don't
have a clue how to download it in the Makefile. There's no mention
of github in /usr/ports/Mk, so I assume the method hasn't even been
written yet. The source is here:
<https://github.com/firnsy/barnyard2/>, but I don't see a tarball,
and I don't know enough about ports to know if it's even possible to
fetch it from github.
Hi Paul,
What about using the ZIP
https://github.com/firnsy/barnyard2/zipball/master
(this will give you the current master branch in a ZIP file)
or a tarball
https://github.com/firnsy/barnyard2/tarball/master
If you want to keep things more stable (since the master branch might
change frequently and break your build), limit yourself to a specific
version. Fortunately this software is using tags for versioning, so
it's easy to get zips from github, e.g.:
https://github.com/firnsy/barnyard2/zipball/v2-1.10
or if you prefer a tarball (which is usually nicer to have)
https://github.com/firnsy/barnyard2/tarball/v2-1.10
Github provides tarballs (and zipballs) for all branches and tags.
See also:
https://github.com/blog/12-tarball-downloads
Hope that helps
How do I handle this?
firnsy-barnyard2-v2-1.10-0-g2f5d496.tar.gz
Is the string at the end (g2f5d496) auto-generated? If so, that's another
problem.
I guess something like this? Sheesh. What a PITA.
PORTNAME= barnyard2-v2
PORTVERSION= 1.10
PKGNAMEPREFIX= firnsy-
PKGNAMESUFFIX= -0-g2f5d496
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
