Prev: FreeBSD Port: opera-10.10.20091120_2
Next: [patch] Integration between portconf and port options
From: cvs-src on 21 Jul 2010 09:08

Good day!
We now have two ports with name 'hydra' in the tree, one in security
category, and one in www.
Both installs file ${PREFIX}/bin/hydra.
I firstly think about asking for add CONFLICTS line, but then come up
to ports tree should not have
two ports with same name.
What you think about this?
_______________________________________________
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: Ashish SHUKLA on 21 Jul 2010 12:47
cvs-src writes:

> Good day!
> We now have two ports with name 'hydra' in the tree, one in security
> category, and one in www.
> Both installs file ${PREFIX}/bin/hydra.
> I firstly think about asking for add CONFLICTS line, but then come up
> to ports tree should not have
> two ports with same name.
> What you think about this?

In case of multiple ports installing files with same name at same path, then
one of them needs to alter the file names by using suffix or prefix, like GNU
projects do when they collide with BSD equivalents by using 'g' as prefix.

HTH
--
Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0
freebsd.org!ashish | http://people.freebsd.org/~ashish/

“Does history record any case in which the majority was right?”
(Robert A. Heinlein, 1973)
From: Ruslan Mahmatkhanov on 21 Jul 2010 13:13
21.07.2010 20:47, Ashish SHUKLA пишет:
> In case of multiple ports installing files with same name at same path, then
> one of them needs to alter the file names by using suffix or prefix, like GNU
> projects do when they collide with BSD equivalents by using 'g' as prefix.

I don't think that prefixing gnu tools is good example.
For example we have native make in /usr/bin and gmake
in /usr/local/bin.And native make is in base system, and
gmake is a port.

So why CONFLICTS needed then for?

And is this ok to have two ports with the same name. I've
searched Porters Handbook for this, but found nothing (i think
it pretty obvious to mention it in docs).
What if want to remove one of then, or update. Which one
will be removed/updated?

Please don't get me wrong, just curious.

--
Regards,
Ruslan
_______________________________________________
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: Ashish SHUKLA on 21 Jul 2010 15:18
Ruslan Mahmatkhanov writes:
> 21.07.2010 20:47, Ashish SHUKLA пишет:
>> In case of multiple ports installing files with same name at same path, then
>> one of them needs to alter the file names by using suffix or prefix, like GNU
>> projects do when they collide with BSD equivalents by using 'g' as prefix.

> I don't think that prefixing gnu tools is good example.
> For example we have native make in /usr/bin and gmake
> in /usr/local/bin.And native make is in base system, and
> gmake is a port.

> So why CONFLICTS needed then for?

IMHO, CONFLICTS are suited for ports which represent same project or forks or
with different options which install files at same places thus can't be
installed side-by-side. e.g. irc/bitlbee and irc/bitlbee-otr, editors/emacs*
ports etc., thats purely my observation.

> And is this ok to have two ports with the same name. I've
> searched Porters Handbook for this, but found nothing (i think
> it pretty obvious to mention it in docs).
> What if want to remove one of then, or update. Which one
> will be removed/updated?

Well, I don't think its good to have two ports with same name, esp. when they
result in same PKGNAME. To distinguish between similar named ports add a
prefix or suffix to them.

> Please don't get me wrong, just curious.

No problems.

% echo 'pkill cat' >curiosity

--
Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0
freebsd.org!ashish | http://people.freebsd.org/~ashish/

“Keep your BitTorrent clients running and make the world a better
place to live in.” (Sir Debarshi Ray, ".signature", 2010)
From: Kurt Jaeger on 21 Jul 2010 16:21
> 21.07.2010 20:47, Ashish SHUKLA ??????????:
> > In case of multiple ports installing files with same name at same path, then
> > one of them needs to alter the file names by using suffix or prefix, like GNU
> > projects do when they collide with BSD equivalents by using 'g' as prefix.
>
> I don't think that prefixing gnu tools is good example.
> For example we have native make in /usr/bin and gmake
> in /usr/local/bin.And native make is in base system, and
> gmake is a port.
>
> So why CONFLICTS needed then for?

It's needed here because both ports install into the same file.

But you are absolutly right, two ports with the same name (hydra)
are also bad. One of the should be changed, e.g. to hydra-webserver.

> And is this ok to have two ports with the same name.

No, it's bad and should be avoided. I'm pretty sure some
portupgrade tool will break.

--
pi(a)opsec.eu +49 171 3101372 10 years to go !
_______________________________________________
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"

 |  Next  |  Last
Pages: 1 2 3
Prev: FreeBSD Port: opera-10.10.20091120_2
Next: [patch] Integration between portconf and port options