Having a package for each value is an odd way of doing it.
Another way would be to have a device for each value, so you have a 1k device, a 2k2 device e.t.c.
Each device using the same symbol and footprint.
But that is also messy.
My solution is to add attributes when I create the component (ic's, diodes, transistors and so), that holds the manufacturer, manu part no, distributor and distributor part no.
Then my BOM ULP automatically fetches those fields and add it to the BOM.
For resistors, the ULP can parse the "usual" values like 4700, 4k7, 4.7k and variants.
It then creates the "real" part number from that. (I use Digikey as supplier and exclusively use resistors from Stackpole Electonics, as their resistor numbering is well-defined. Also, the Digikey part # version is well definined.)
I once made board for a client who used parts from a fixed part library.
These were numbered like 040301 or so. This partnumber was in a database together with ALL information about that part, description, price, distributor, manufacturer e.t.c.
The database was maintained by a program, which name I sadly have forgotten.
I created a new component library that contained an attribute for PARTNO, and printed that on the symbol under the VALUE. It was then easy to see both the real component value as well as the special partno.
It was a little extra work to add the partno, but not much, and it paid well off later.
I could then autogenerate BOMs that had ALL details about the part, total price for the # of assemblies e.t.c.
Ready to order. Pretty neat.
