Bug 207810 - [NEW PORT] ports-mgmt/portest: Patch file automation for FreeBSD-ports
Summary: [NEW PORT] ports-mgmt/portest: Patch file automation for FreeBSD-ports
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kurt Jaeger
URL: https://github.com/Ultima1252/portest
Keywords: easy, patch-ready
Depends on:
Blocks:
 
Reported: 2016-03-08 15:26 UTC by Ultima
Modified: 2016-03-08 17:50 UTC (History)
3 users (show)

See Also:
Ultima1252: maintainer-feedback+


Attachments
portest.diff (3.05 KB, patch)
2016-03-08 15:26 UTC, Ultima
Ultima1252: maintainer-approval+
Details | Diff
portest.shar (1.73 KB, application/x-shar)
2016-03-08 15:46 UTC, Ultima
Ultima1252: maintainer-approval+
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ultima 2016-03-08 15:26:10 UTC
Created attachment 167857 [details]
portest.diff

With portest, you can create, update, patch and revert a port tree with
svn, git and portsnap. Portest can also do portlint testing, test a port
with port test, or poudriere, and also generate a list of ports a
patchfile(s) will modify. Portest is written in shell with minimal
dependencies mostly using FreeBSD-base

WWW: https://github.com/Ultima1252/portest
Comment 1 Torsten Zühlsdorff 2016-03-08 15:30:38 UTC
Hello Ricky,

can you please provide a shar instead of an diff. A shar is the common way to provide a new port :)

Greetings,
Torsten
Comment 2 Ultima 2016-03-08 15:46:33 UTC
Created attachment 167859 [details]
portest.shar
Comment 3 Chris Hutchinson 2016-03-08 16:08:02 UTC
(In reply to Ultima from comment #2)
> Created attachment 167859 [details]
> portest.shar

Doesn't bugzilla know that shar(1) files are of text/plain?

--Chris

P.S. Looks like a great tool, Ultima!
Comment 4 Torsten Zühlsdorff 2016-03-08 16:11:27 UTC
(In reply to Chris Hutchinson from comment #3)

> Doesn't bugzilla know that shar(1) files are of text/plain?

I must protect bugzilla, because it did it right. I declared the mime type "application/x-shar". Often the browser itself does not know, that you can view this as text and offers a download of this file.

Of course you can teach your browser to do this. But first it is very annoying :D

Greetings,
Torsten
Comment 5 Ultima 2016-03-08 16:26:55 UTC
(In reply to Chris Hutchinson from comment #3)
> Doesn't bugzilla know that shar(1) files are of text/plain?

Yeah, thats why I don't care for shars, but it is the correct way according to handbook. I did forget to add the entry to the Makefile in the diff tho >.<


> P.S. Looks like a great tool, Ultima!

Thanks, I hope it is helpful. I use it constantly when working on ports. It cuts down much of time with repetitive commands.
Comment 6 Chris Hutchinson 2016-03-08 16:44:12 UTC
(In reply to Torsten Zühlsdorff from comment #4)
> (In reply to Chris Hutchinson from comment #3)
> 
> > Doesn't bugzilla know that shar(1) files are of text/plain?
> 
> I must protect bugzilla, because it did it right. I declared the mime type
> "application/x-shar". Often the browser itself does not know, that you can
> view this as text and offers a download of this file.
Yes. You can never trust those evil text/plain files. ;)
> 
> Of course you can teach your browser to do this. But first it is very
> annoying :D
Aren't you the clever one. See how you just made
this *my* responsibility. ;) ;)

Point taken. Thanks, Torsten!

--Chris
Comment 7 Chris Hutchinson 2016-03-08 16:47:40 UTC
(In reply to Ultima from comment #5)
> (In reply to Chris Hutchinson from comment #3)
> > Doesn't bugzilla know that shar(1) files are of text/plain?
> 
> Yeah, thats why I don't care for shars, but it is the correct way according
> to handbook. I did forget to add the entry to the Makefile in the diff tho
> >.<
> 
> 
> > P.S. Looks like a great tool, Ultima!
> 
> Thanks, I hope it is helpful. I use it constantly when working on ports. It
> cuts down much of time with repetitive commands.

Looking forward to taking this for a spin. :)

Is it just my copy, or is the attached shar(1) missing
portest/pkg-descr ?

--Chris
Comment 8 Ultima 2016-03-08 17:06:37 UTC
(In reply to Chris Hutchinson from comment #7)

> Looking forward to taking this for a spin. :)

Awesome! If you have any suggestions or problems feel free to email me. I'm eager feedback! =]

> Is it just my copy, or is the attached shar(1) missing
portest/pkg-descr ?
It is at the top, the first file.
Comment 9 Kurt Jaeger freebsd_committer 2016-03-08 17:26:45 UTC
Well, I don't buy the 'minimal depends' 8-}, test-building right now and it
pulls in at least 24 other ports with the default OPTIONS, like perl, subversion, and git.
Comment 10 Kurt Jaeger freebsd_committer 2016-03-08 17:48:37 UTC
Testbuilds are fine.
Comment 11 commit-hook freebsd_committer 2016-03-08 17:49:55 UTC
A commit references this bug:

Author: pi
Date: Tue Mar  8 17:49:45 UTC 2016
New revision: 410637
URL: https://svnweb.freebsd.org/changeset/ports/410637

Log:
  New port: ports-mgmt/portest

  With portest, you can create, update, patch and revert a port tree with
  svn, git and portsnap. Portest can also do portlint testing, test a port
  with port test, or poudriere, and also generate a list of ports a
  patchfile(s) will modify. Portest is written in shell with minimal
  dependencies mostly using FreeBSD-base

  WWW: https://github.com/Ultima1252/portest

  PR:		207810
  Submitted by:	Ultima1252@gmail.com

Changes:
  head/ports-mgmt/Makefile
  head/ports-mgmt/portest/
  head/ports-mgmt/portest/Makefile
  head/ports-mgmt/portest/distinfo
  head/ports-mgmt/portest/pkg-descr
Comment 12 Kurt Jaeger freebsd_committer 2016-03-08 17:50:42 UTC
Committed, thanks!