--KN5l+BnMqAQyZLvT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

hi,

On Wed, Feb 19, 2003 at 02:22:08PM +1100, Adrian Portelli wrote:
>=20
> Anyone got an idea about how to deal with two packages with the same
> name ?
>=20
> There is currently a net/arpd package and I'm creating a package for
> honeyd (http://www.citi.umich.edu/u/provos/honeyd/).
>=20
> Honeyd has a supporting program also called arpd which is distributed
> separately.  So how do I go about adding honeyd's arpd package without
> conflicting with the current one in pkgsrc ?
>=20
> I suppose I could put it under 'security' instead of 'net'.  Maybe
> net/arpd-honeyd ???

the common practice of dealing with such situations is rename the new
package and either make them conflict or alter names of the conflicting
files.  in this case the latter is probably way to go.  then you need to
make sure the other dependent packages are actually using the new
renamed files, of course.

as an alternative solution, you can ask Niels (i added him on cc:) to
change name of the arpd package and daemon.  arpd is too generic name
and it's expected to cause conflicts.  maybe harpd, honeyarpd or
honey-arpd would be better.


regards,

--=20
-- Lubomir Sedlacik <salo@Xtrmntr.org>                   --
--                  <salo@silcnet.org>                   --

--KN5l+BnMqAQyZLvT
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (NetBSD)

iD8DBQE+Uwa3iwjDDlS8cmMRAsfgAJ4gOcYjkH5A1yTlcKM4a2e659FHdQCcCHpL
3riGj0W0i90T5bzNmxxmY3k=
=llT4
-----END PGP SIGNATURE-----

--KN5l+BnMqAQyZLvT--