Prev: INDEX now builds successfully on 6.x
Next: Simple hack to get $500 to your home.
From: "b. f." on 6 Jun 2010 21:47
On 6/7/10, b. f. <bf1783(a)googlemail.com> wrote:

> You can keep the script in a location other than
> /usr/ports/devel/bar/pkg-req, just by using something like:
>
> .if${.CURDIR:M*/usr/ports/devel/bar*}
> PKGREQ="insert full path to script here"
> .endif
>
> in /etc/make.conf, because /usr/ports/Mk/bsd.port.mk will use PKGREQ
> along with the -r flag in the "do-package" target.

That is, in the "do-package" target when making a package, and in the
"fake-pkg" target when installing a port.

b.
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Garrett Cooper on 7 Jun 2010 10:18
On Sun, Jun 6, 2010 at 4:53 PM, Thomas Rasmussen <thomas(a)gibfest.dk> wrote:
> Hello,
>
> I've been wondering about something: When I write a script or webapp that
> needs some port to run, like a perl module, I install the needed port and
> life is good (tm). A year later when I've completely forgotten about the
> script I go do some spring-cleaning of the ports on the server, and I see
> some perl module that doesn't have any dependencies, and delete it. Fast
> forward a few days when I discover the script doesn't work anymore, cue
> face-palm, remove bullet from foot, etc.
>
> Is there some way I can register a dependency to prevent this ? Like
> adding a flag to an installed port to say "something outside of the ports
> system depends on this" along with a user specified comment string. A
> system like that could result in something like this:
>
> pkg_delete -x p5-something
> pkg_delete: p5-something cant be uninstalled because: "somescript.pl uses
> this module, for the love of everything good do not delete it"
>
> Is something like this already implemented, or does anyone have suggestions
> to where I might begin if I want to make this ? Am I the only FreeBSD
> admin absent-minded enough to have this problem ? :)
>
> Best regards
>
> Thomas Steen Rasmussen
>
> PS: I know that this kind of hand-holding is uncommon in FreeBSD. We
> allow all kinds of foot-shooting, but a safeguard like this would be a nice
> improvement to an (IMO) already excellent ports system.

It would probably just be better to create ports Makefiles for
this and then run a make install ; that way you have all of the
required metadata for the package you just created. If you go this
route you'll need several skeleton files to create a complete port.
You can look at any port, or here's another simple example port (
http://p4db.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/gcooper/ports/devel/atf&HIDEDEL=NO
). Feel free to skip the pkg-deinstall script.
HTH,
-Garrett
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: RW on 7 Jun 2010 12:34
On Mon, 07 Jun 2010 08:53:53 +0100
Matthew Seaman <m.seaman(a)infracaninophile.co.uk> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/06/2010 02:10:33, Stephen Montgomery-Smith wrote:
> > Stephen Montgomery-Smith wrote:
>

> > So --- this is what I would do. If I had a set of scripts that I
> > wanted to install, I would write my own local port whose job is to
> > install the scripts, and which lists the needed dependencies as
> > RUN_DEPENDS.
>
> So, you're creating your own meta-port that exists only to be depended
> on by the ports you specifically want to have installed? That's a
> really good idea. You might need to fill out the contents of your
> "wanted-ports" meta-port a bit more, but the concept seems sound to
> me.
>
> It shouldn't cause horrendous problems with most package tools -- they
> all cope with things like bsdpan- ports already, which don't have any
> directory in the ports tree.

If it's a metaport then it does have an origin.
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Matthew Seaman on 7 Jun 2010 13:04
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/2010 17:34:39, RW wrote:
> If it's a metaport then it does have an origin.

It certainly needs an origin if some other port is going to depend on
it. Which is usually the case for metaports, but not necessarily so.

Cheers,

Matthew

- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew(a)infracaninophile.co.uk Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwNJqUACgkQ8Mjk52CukIwcSwCdHT0BscVpQyuAvhhQX6CGy6rb
BVwAn2fxTbhUHV3zWHMZRHAhSqxxd2ck
=fUny
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: RW on 8 Jun 2010 07:36
On Mon, 07 Jun 2010 18:04:37 +0100
Matthew Seaman <m.seaman(a)infracaninophile.co.uk> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/06/2010 17:34:39, RW wrote:
> > If it's a metaport then it does have an origin.
>
> It certainly needs an origin if some other port is going to depend on
> it. Which is usually the case for metaports, but not necessarily so.

A metaport is a port and has an origin by definition. What you are
referring to is a metapackage.
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: INDEX now builds successfully on 6.x
Next: Simple hack to get $500 to your home.